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

Integrate with Google Cloud to spin up/down droplet #4

Open
proegssilb opened this issue Nov 5, 2020 · 1 comment
Open

Integrate with Google Cloud to spin up/down droplet #4

proegssilb opened this issue Nov 5, 2020 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@proegssilb
Copy link
Owner

DigitalOcean is my preferred "first pass" cloud provider; they've got a really simple system.

The core mechanics of any cloud integration is tracking volumes for server config and save data, and then using those volumes to create droplets for the servers at the right time.

This issue is just for the basic "being able to spin up/down a droplet", not for getting that hooked up to much of anything.

@proegssilb proegssilb added this to the v0.0.2 - The Basics milestone Nov 23, 2020
@proegssilb proegssilb added the enhancement New feature or request label Nov 23, 2020
@proegssilb proegssilb self-assigned this May 20, 2021
@proegssilb proegssilb changed the title Integrate with Digital Ocean to spin up/down droplet Integrate with Google Cloud to spin up/down droplet May 22, 2021
@proegssilb
Copy link
Owner Author

In #30, I created an operator for this. However, in order to actually call this issue done, there needs to be code to go with, so that how to use the operator correctly isn't a valid question.

In general, there's 4 verbs associated with the life cycle of each game:

  • Create/Destroy
  • Spin Up/Spin Down

Note that each verb is paired, and there's effectively two levels of bracketing going on. Create and Destroy mark the life of the game, and Spin Up/Spin Down mark the life of each session.

For now, that's as much as the web app cares about. There's conversation you can have about the states these transitions define, but I don't think we need to worry about tracking that. Just provide those 4 transitions, it'll probably be fine.

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

No branches or pull requests

1 participant