-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Added HA capability to the VMs during VMware Host alert #7352
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
Added HA capability to the VMs during VMware Host alert #7352
Conversation
|
@blueorangutan package |
weizhouapache
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does Alert state mean the vmware host is Down ?
It is very risky to start 1 vm on 2 hosts, which might cause data corruption.
|
I get your point @weizhouapache and that seems to be correct. And I now really see why HA is not implemented for VMware, we need to check the actual status of VM. I think we can do it by implementing CheckOnHostCommand Lines 5685 to 5687 in d04d60b
This does check the VM state using the neighbour hosts in the cluster (thats how it is impletemented in KVM) For now, I'm marking this PR as draft. @weizhouapache please let me know if CheckOnHostCommand makes some sense ! |
@harikrishna-patnala |
shwstppr
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some options in my opinion @harikrishna-patnala @weizhouapache @rohityadavcloud
- We can have global config for a timeout after which all VMs on an Alert state host are migrated away
- We allow putting such host in maintenance so the operator can manually put it in maintenance so the VMs on the host get migrated away
|
ping @harikrishna-patnala any update on this? Thanks. |
|
ping @harikrishna-patnala @shwstppr any update on this? Thanks. |
|
I like the idea of @shwstppr to add an global setting to attempt migrate the VMs when host goes to alert state. I'll add that and update the PR. |
|
So if I understand @shwstppr correctly we will implement a setting to time putting hosts in Alert state in Maintenance. Migrating of VMs should then automatically happen and we should not have to care about that. Is that correct @shwstppr ? I wonder if this takes @weizhouapache 's worry away. The host in alert state may still be up, and as it can not be reached, the VMs on it cannot be stopped or migrated. The disks may consequently still be accessed and modified by any process running on the VM (started by cron or as a deamon (or windows equivilents)) Can we leverage vSphere HA for this (https://www.techtarget.com/searchvmware/definition/VMware-HA)? |
|
I think we should not merge this. I created a doc PR at apache/cloudstack-documentation#324 . If we can improve the functional description of this we may be able to implement some added HA functionality but relying on a timeout is error prone. Even if the operator is sure the VMs are no longer running, CloudStack cannot. |
|
Agree with you @DaanHoogland, closing this PR for that reason. |
Description
This PR tries to fix #7320 where it adds improvement to handle VMs HA when VMware host goes into alert state.
Usually, VMware hosts go to alert state when ping times out. So it is good idea to start HA process on the VMs residing on the host.
Types of changes
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
Bug Severity
Screenshots (if appropriate):
How Has This Been Tested?