Skip to content
This repository has been archived by the owner on Mar 19, 2019. It is now read-only.

Migration of Squirrels #21

Open
AndreasAakesson opened this issue Jun 16, 2016 · 2 comments
Open

Migration of Squirrels #21

AndreasAakesson opened this issue Jun 16, 2016 · 2 comments

Comments

@AndreasAakesson
Copy link
Contributor

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?

@alfreb
Copy link
Contributor

alfreb commented Jun 16, 2016

I'd suggest putting in the URL to migration server via a file on the memdisk and just do it once at boot.

@alfreb
Copy link
Contributor

alfreb commented Jun 16, 2016

Later we can add it as a parameter to openstack- I know how we can get that into the instance

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants