[
https://issues.apache.org/jira/browse/CLOUDSTACK-10449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nux updated CLOUDSTACK-10449:
-----------------------------
Labels: gsoc2022 mentor new-feature (was: gsoc2022 new-feature)
> GSoC 2022 Idea: Keep track of VM's "last known state" and enforce it after an
> outage
> ------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-10449
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10449
> Project: CloudStack
> Issue Type: New Feature
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Reporter: Nux
> Priority: Minor
> Labels: gsoc2022, mentor, new-feature
>
> An infrastructure outage can take out several or all VMs. In the aftermath
> it's not always possible to know which VMs were supposed to be ON or OFF,
> especially if HA is not enabled. People keep powered off VMs around all the
> time for many reasons.
> I propose we add a feature where Cloudstack keeps track of the "last known
> state" of a VM and after an outage either enforce it (ie start the VM or
> leave it off) or at least show some information to the operator in the UI/API
> so they can do it themselves; perhaps make this behaviour configurable in the
> global settings.
> Thanks
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
