You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 19, 2019. It is now read-only.
Acorn is currently not stable enough to not crash, but good enough to run on OpenStack.
It's fun to see users capturing new Squirrels 😸 , but sad to see them escape when the VM dies 😿 .
My current idea is something like this:
Create a route to something like /api/squirrels/migrate/:ip (or ?ip= until parsing is implemented)
When booting a new instance with a clean Bucket, the "admin" just enters http://<current instance>/api/squirrels/migrate/<old instance>, and all the squirrels will clone and jump into the new bucket.
To avoid being exploited, we just add an bool if it's been a migration, if true, just return 404 (or a more suited status code).
This will not help if the old instance has already crashed tho (which it shouldn't soon™).
Any better ideas?
The text was updated successfully, but these errors were encountered:
Acorn is currently not stable enough to not crash, but good enough to run on OpenStack.
It's fun to see users capturing new Squirrels 😸 , but sad to see them escape when the VM dies 😿 .
My current idea is something like this:
/api/squirrels/migrate/:ip
(or?ip=
until parsing is implemented)http://<current instance>/api/squirrels/migrate/<old instance>
, and all the squirrels will clone and jump into the new bucket.true
, just return 404 (or a more suited status code).This will not help if the old instance has already crashed tho (which it shouldn't soon™).
Any better ideas?
The text was updated successfully, but these errors were encountered: