There should be an ability to set auto boot (restart) for VMs with local storage, i.e. similar functionality as ´virsh autostart VM´ in KVM.
When a server reboot occurs, for instance if heartbeat on the host can't write to NFS share, the server will reboot. In current versions of cloudstack, all instances using local storage on that host will need to be manually started after the reboot. There should be a functionality to mark VMs to be auto started when the host is live again.
This is particularly useful when a compute instance is using local storage (SSDs) for system disk, but NFS etc. for data storage, or when not using networked attached storage but local storage only configurations.
This is functionality similar to what is requested in #8687
STEPS TO REPRODUCE
Example of possible implementation:
- UI and API option for compute instance to auto boot on host startup (enable/disable feature per compute instance).
- Mgmt server to issue startup of compute instances when Host is ready.
EXPECTED RESULTS
Compute instances with local storage should be able able to auto start (if configured) when a host is live again after reboot.
ACTUAL RESULTS
Currently all local storage compute instances needs to be manually started after host reboot.
ISSUE TYPE
COMPONENT NAME
CLOUDSTACK VERSION
CONFIGURATION
N/A
OS / ENVIRONMENT
N/A
SUMMARY
There should be an ability to set auto boot (restart) for VMs with local storage, i.e. similar functionality as ´virsh autostart VM´ in KVM.
When a server reboot occurs, for instance if heartbeat on the host can't write to NFS share, the server will reboot. In current versions of cloudstack, all instances using local storage on that host will need to be manually started after the reboot. There should be a functionality to mark VMs to be auto started when the host is live again.
This is particularly useful when a compute instance is using local storage (SSDs) for system disk, but NFS etc. for data storage, or when not using networked attached storage but local storage only configurations.
This is functionality similar to what is requested in #8687
STEPS TO REPRODUCE
EXPECTED RESULTS
ACTUAL RESULTS