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

Support API for stopping all running instances in a certain sled or all sleds #4746

Open
askfongjojo opened this issue Jan 2, 2024 · 0 comments

Comments

@askfongjojo
Copy link

Until sled-agent supports the mechanism of re-spinning propolis zones after they've been bounced or purged (omicron#3633) and live migration can be used in the field, stopping and starting VMs is the only way to evacuate VMs prior to sled SW/HW maintenance. Currently, neither Oxide technician nor operators can stop VMs on behalf of their owners. We'll need this ability to avoid telling users to force their VMs to failed state, then delete and create them again (from a customer pov, VMs are "broken" after software update).

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