Global maintenance and fencing of hosts
I am wondering whether global maintenance inhibits fencing of non-responsive hosts. Is this so? Background: I plan on migrating the engine from one cluster to another. I understand this means to backup/restore the engine. While migrating the engine it is shut down and all VMs will continue running. This is good. When starting the engine in the new location, I really don't want the engine to fence any host on its own, because of reasons I can not yet know. So is global maintenance enough to suppress fencing, or do I have to deactivate fencing on all hosts?
On Fri, Apr 12, 2019, 12:53 Andreas Elvers < andreas.elvers+ovirtforum@solutions.work> wrote:
I am wondering whether global maintenance inhibits fencing of non-responsive hosts. Is this so?
Background: I plan on migrating the engine from one cluster to another. I understand this means to backup/restore the engine. While migrating the engine it is shut down and all VMs will continue running. This is good. When starting the engine in the new location, I really don't want the engine to fence any host on its own, because of reasons I can not yet know.
So is global maintenance enough to suppress fencing, or do I have to deactivate fencing on all hosts?
Global maintenance disables fencing.
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/3KRJRAWBFC4QAX...
On Fri, Apr 12, 2019 at 10:18 PM Alex K <rightkicktech@gmail.com> wrote:
On Fri, Apr 12, 2019, 12:53 Andreas Elvers < andreas.elvers+ovirtforum@solutions.work> wrote:
I am wondering whether global maintenance inhibits fencing of non-responsive hosts. Is this so?
Background: I plan on migrating the engine from one cluster to another. I understand this means to backup/restore the engine. While migrating the engine it is shut down and all VMs will continue running. This is good. When starting the engine in the new location, I really don't want the engine to fence any host on its own, because of reasons I can not yet know.
So is global maintenance enough to suppress fencing, or do I have to deactivate fencing on all hosts?
Global maintenance disables fencing.
This is not really true; on the other side on the automated restore flow we are also automatically disabling the fencing mechanism exactly for the reason that Andreas mentioned: https://github.com/oVirt/ovirt-ansible-hosted-engine-setup/blob/master/tasks... Fencing will be automatically re-enabled at the end of the restore process when we are sure that the just restored engine is correctly working.
_______________________________________________
Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/3KRJRAWBFC4QAX...
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/6N7W56J63WQY76...
participants (3)
-
Alex K -
Andreas Elvers -
Simone Tiraboschi