acorn
acorn copied to clipboard
Migration of Squirrels
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?
I'd suggest putting in the URL to migration server via a file on the memdisk and just do it once at boot.
Later we can add it as a parameter to openstack- I know how we can get that into the instance