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

Migration of Squirrels #21

@AndreasAakesson

Description

@AndreasAakesson

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?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions