Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Replace VPS swap by giving playground VPS addresses from production #9

Closed
aither64 opened this issue Jun 29, 2020 · 1 comment
Closed

Comments

@aither64
Copy link
Member

Right now, VPS swap is needed, because playground is using different address ranges than production. So we use swap to put the new VPS into production and give it addresses from the original production VPS and vice versa. This operation was always very hard to grasp, explain and implement, so it should be retired.

We could instead ask the user for a purpose when creating/cloning a playground VPS: does he want a VPS that will later be put in production? Does he want to try something out and forget it? If the VPS is meant to be used in production, we'd give it addresses from production immediately and then it's simply a matter of migrating it onto production node -- IP addresses will be kept. It will make so much more sense to prepare a new VPS next to the old one, slowly move services over, etc. and not having to deal with IP changes.

@aither64
Copy link
Member Author

Giving playground VPS addresses from production is now possible, although afaik only by admins. Swap on vpsAdminOS has been implemented anyways, so closing.

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

No branches or pull requests

1 participant