[Users] High Availability
What should I need to configure to put HA working? I mean, when a host broke all the VM automatically move to another host. Do I need to have Power management enabled? Thanks
Currently it only applies to server VMs Go to Add/Edit VM dialogue -> High Availability tab -> mark the check box. and you are done. If this interests you stay on the lookout for: http://www.ovirt.org/Features/Watchdog_engine_support Noam. ----- Original Message ----- From: suporte@logicworks.pt To: Users@ovirt.org Sent: Sunday, March 17, 2013 6:27:53 PM Subject: [Users] High Availability What should I need to configure to put HA working? I mean, when a host broke all the VM automatically move to another host. Do I need to have Power management enabled? Thanks _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Hi, You have to configure power management to make high availability working and mark the vms high availability checkbox... Regards, René -----Original message-----
From:suporte@logicworks.pt <suporte@logicworks.pt> Sent: Sunday 17th March 2013 17:28 To: Users@ovirt.org Subject: [Users] High Availability
What should I need to configure to put HA working? I mean, when a host broke all the VM automatically move to another host. Do I need to have Power management enabled?
Thanks _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Is it Mandatory to have power manamement enabled? if yes what equipment do you recommend to use with it? Regards Jose ----- Mensagem original ----- De: "René Koch" <r.koch@ovido.at> Para: suporte@logicworks.pt, Users@ovirt.org Enviadas: Domingo, 17 Março, 2013 16:47:41 Assunto: RE: [Users] High Availability Hi, You have to configure power management to make high availability working and mark the vms high availability checkbox... Regards, René -----Original message-----
From:suporte@logicworks.pt <suporte@logicworks.pt> Sent: Sunday 17th March 2013 17:28 To: Users@ovirt.org Subject: [Users] High Availability
What should I need to configure to put HA working? I mean, when a host broke all the VM automatically move to another host. Do I need to have Power management enabled?
Thanks _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
I think that there is some confusion here so I will explain what are the configurations for fail-over. power management will reboot your host if a connectivity issue is detected so all your vm's will be killed. resilience policy will allow you to choose vm migration policy during a host failure and its configured in the cluster level (clusters -> select cluster -> general sub tab -> edit policy) High Availability is configured only for servers type vm's and what it does is re-run the vm in case the pid of the vm is killed (so most commonly, if you have power management configured, and the host is rebooted, the vm will start automatically on a different host). so it really depends what you want. if you want vm migration than look into cluster policy, if you want a specific vm to always be up and you don't care about the other vm's than configure power management and a HA vm. it really depends on what you need. On 03/17/2013 07:15 PM, suporte@logicworks.pt wrote:
Is it Mandatory to have power manamement enabled? if yes what equipment do you recommend to use with it?
Regards Jose
----- Mensagem original ----- De: "René Koch" <r.koch@ovido.at> Para: suporte@logicworks.pt, Users@ovirt.org Enviadas: Domingo, 17 Março, 2013 16:47:41 Assunto: RE: [Users] High Availability
Hi,
You have to configure power management to make high availability working and mark the vms high availability checkbox...
Regards, René
-----Original message-----
From:suporte@logicworks.pt <suporte@logicworks.pt> Sent: Sunday 17th March 2013 17:28 To: Users@ovirt.org Subject: [Users] High Availability
What should I need to configure to put HA working? I mean, when a host broke all the VM automatically move to another host. Do I need to have Power management enabled?
Thanks _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
-- Dafna Ron
You might also find this helpful: https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Virtualiza... The topics before and after it explain a bit more about high availability. Tim Hildred, RHCE Content Author II - Engineering Content Services, Red Hat, Inc. Brisbane, Australia Email: thildred@redhat.com Internal: 8588287 Mobile: +61 4 666 25242 IRC: thildred ----- Original Message -----
From: "Dafna Ron" <dron@redhat.com> To: suporte@logicworks.pt Cc: Users@ovirt.org Sent: Monday, March 18, 2013 4:46:51 AM Subject: Re: [Users] High Availability
I think that there is some confusion here so I will explain what are the configurations for fail-over.
power management will reboot your host if a connectivity issue is detected so all your vm's will be killed. resilience policy will allow you to choose vm migration policy during a host failure and its configured in the cluster level (clusters -> select cluster -> general sub tab -> edit policy) High Availability is configured only for servers type vm's and what it does is re-run the vm in case the pid of the vm is killed (so most commonly, if you have power management configured, and the host is rebooted, the vm will start automatically on a different host).
so it really depends what you want. if you want vm migration than look into cluster policy, if you want a specific vm to always be up and you don't care about the other vm's than configure power management and a HA vm. it really depends on what you need.
On 03/17/2013 07:15 PM, suporte@logicworks.pt wrote:
Is it Mandatory to have power manamement enabled? if yes what equipment do you recommend to use with it?
Regards Jose
----- Mensagem original ----- De: "René Koch" <r.koch@ovido.at> Para: suporte@logicworks.pt, Users@ovirt.org Enviadas: Domingo, 17 Março, 2013 16:47:41 Assunto: RE: [Users] High Availability
Hi,
You have to configure power management to make high availability working and mark the vms high availability checkbox...
Regards, René
-----Original message-----
From:suporte@logicworks.pt <suporte@logicworks.pt> Sent: Sunday 17th March 2013 17:28 To: Users@ovirt.org Subject: [Users] High Availability
What should I need to configure to put HA working? I mean, when a host broke all the VM automatically move to another host. Do I need to have Power management enabled?
Thanks _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
-- Dafna Ron _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
This is a multi-part message in MIME format. --------------010000090502070605080205 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Tim, Thanks for your information. I am not sure why we need power management to be configured for the hosts running HA virtual machines. If one host is down because of network interrupt or power failure, the engine should know how many HA VMs are down and find out the VM images on the storage domain to start the VM instances on another host in the cluster. Why do we need power manager to be configured? We only need a method to check the VM or host status and a method to restart the VM instances with existing VM images on another host. Is it required to force powering down the failing host forever to make sure the failing host will not come back to live again? * Power management must be configured for the hosts running the highly available virtual machines. * The host running the highly available virtual machine must be part of a cluster which has other available hosts. * The destination host must be running. * The source and destination host must have access to the data domain on which the virtual machine resides. * The source and destination host must have access to the same virtual networks and VLANs. * There must be enough CPUs on the destination host that are not in use to support the virtual machine's requirements. * There must be enough RAM on the destination host that is not in use to support the virtual machine's requirements. Tim Hildred:
You might also find this helpful: https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Virtualiza...
The topics before and after it explain a bit more about high availability.
Tim Hildred, RHCE Content Author II - Engineering Content Services, Red Hat, Inc. Brisbane, Australia Email: thildred@redhat.com Internal: 8588287 Mobile: +61 4 666 25242 IRC: thildred
----- Original Message -----
From: "Dafna Ron" <dron@redhat.com> To: suporte@logicworks.pt Cc: Users@ovirt.org Sent: Monday, March 18, 2013 4:46:51 AM Subject: Re: [Users] High Availability
I think that there is some confusion here so I will explain what are the configurations for fail-over.
power management will reboot your host if a connectivity issue is detected so all your vm's will be killed. resilience policy will allow you to choose vm migration policy during a host failure and its configured in the cluster level (clusters -> select cluster -> general sub tab -> edit policy) High Availability is configured only for servers type vm's and what it does is re-run the vm in case the pid of the vm is killed (so most commonly, if you have power management configured, and the host is rebooted, the vm will start automatically on a different host).
so it really depends what you want. if you want vm migration than look into cluster policy, if you want a specific vm to always be up and you don't care about the other vm's than configure power management and a HA vm. it really depends on what you need.
On 03/17/2013 07:15 PM, suporte@logicworks.pt wrote:
Is it Mandatory to have power manamement enabled? if yes what equipment do you recommend to use with it?
Regards Jose
----- Mensagem original ----- De: "René Koch" <r.koch@ovido.at> Para: suporte@logicworks.pt, Users@ovirt.org Enviadas: Domingo, 17 Março, 2013 16:47:41 Assunto: RE: [Users] High Availability
Hi,
You have to configure power management to make high availability working and mark the vms high availability checkbox...
Regards, René
-----Original message-----
From:suporte@logicworks.pt <suporte@logicworks.pt> Sent: Sunday 17th March 2013 17:28 To: Users@ovirt.org Subject: [Users] High Availability
What should I need to configure to put HA working? I mean, when a host broke all the VM automatically move to another host. Do I need to have Power management enabled?
Thanks _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
-- Dafna Ron _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
-- --- 舒明 Shu Ming Open Virtualization Engineerning; CSTL, IBM Corp. Tel: 86-10-82451626 Tieline: 9051626 E-mail: shuming@cn.ibm.com or shuming@linux.vnet.ibm.com Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District, Beijing 100193, PRC --------------010000090502070605080205 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit <html> <head> <meta content="text/html; charset=UTF-8" http-equiv="Content-Type"> </head> <body text="#000000" bgcolor="#FFFFFF"> <div class="moz-cite-prefix">Tim,<br> <br> Thanks for your information. I am not sure why we need power management to be configured for the hosts running HA virtual machines. If one host is down because of network interrupt or power failure, the engine should know how many HA VMs are down and find out the VM images on the storage domain to start the VM instances on another host in the cluster. Why do we need power manager to be configured? We only need a method to check the VM or host status and a method to restart the VM instances with existing VM images on another host. Is it required to force powering down the failing host forever to make sure the failing host will not come back to live again?<br> <br> <br> <ul> <li class="listitem"> <div class="para">Power management must be configured for the hosts running the highly available virtual machines. </div> </li> <li class="listitem"> <div class="para"> The host running the highly available virtual machine must be part of a cluster which has other available hosts. </div> </li> <li class="listitem"> <div class="para"> The destination host must be running. </div> </li> <li class="listitem"> <div class="para"> The source and destination host must have access to the data domain on which the virtual machine resides. </div> </li> <li class="listitem"> <div class="para"> The source and destination host must have access to the same virtual networks and VLANs. </div> </li> <li class="listitem"> <div class="para"> There must be enough CPUs on the destination host that are not in use to support the virtual machine's requirements. </div> </li> <li class="listitem"> <div class="para"> There must be enough RAM on the destination host that is not in use to support the virtual machine's requirements. </div> </li> </ul> <br> <br> Tim Hildred:<br> </div> <blockquote cite="mid:646344375.46855977.1363573783397.JavaMail.root@redhat.com" type="cite"> <pre wrap="">You might also find this helpful: <a class="moz-txt-link-freetext" href="https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Virtualization/3.1/html/Administration_Guide/High_availability_considerations.html">https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Virtualization/3.1/html/Administration_Guide/High_availability_considerations.html</a> The topics before and after it explain a bit more about high availability. Tim Hildred, RHCE Content Author II - Engineering Content Services, Red Hat, Inc. Brisbane, Australia Email: <a class="moz-txt-link-abbreviated" href="mailto:thildred@redhat.com">thildred@redhat.com</a> Internal: 8588287 Mobile: +61 4 666 25242 IRC: thildred ----- Original Message ----- </pre> <blockquote type="cite"> <pre wrap="">From: "Dafna Ron" <a class="moz-txt-link-rfc2396E" href="mailto:dron@redhat.com"><dron@redhat.com></a> To: <a class="moz-txt-link-abbreviated" href="mailto:suporte@logicworks.pt">suporte@logicworks.pt</a> Cc: <a class="moz-txt-link-abbreviated" href="mailto:Users@ovirt.org">Users@ovirt.org</a> Sent: Monday, March 18, 2013 4:46:51 AM Subject: Re: [Users] High Availability I think that there is some confusion here so I will explain what are the configurations for fail-over. power management will reboot your host if a connectivity issue is detected so all your vm's will be killed. resilience policy will allow you to choose vm migration policy during a host failure and its configured in the cluster level (clusters -> select cluster -> general sub tab -> edit policy) High Availability is configured only for servers type vm's and what it does is re-run the vm in case the pid of the vm is killed (so most commonly, if you have power management configured, and the host is rebooted, the vm will start automatically on a different host). so it really depends what you want. if you want vm migration than look into cluster policy, if you want a specific vm to always be up and you don't care about the other vm's than configure power management and a HA vm. it really depends on what you need. On 03/17/2013 07:15 PM, <a class="moz-txt-link-abbreviated" href="mailto:suporte@logicworks.pt">suporte@logicworks.pt</a> wrote: </pre> <blockquote type="cite"> <pre wrap="">Is it Mandatory to have power manamement enabled? if yes what equipment do you recommend to use with it? Regards Jose ----- Mensagem original ----- De: "René Koch" <a class="moz-txt-link-rfc2396E" href="mailto:r.koch@ovido.at"><r.koch@ovido.at></a> Para: <a class="moz-txt-link-abbreviated" href="mailto:suporte@logicworks.pt">suporte@logicworks.pt</a>, <a class="moz-txt-link-abbreviated" href="mailto:Users@ovirt.org">Users@ovirt.org</a> Enviadas: Domingo, 17 Março, 2013 16:47:41 Assunto: RE: [Users] High Availability Hi, You have to configure power management to make high availability working and mark the vms high availability checkbox... Regards, René -----Original message----- </pre> <blockquote type="cite"> <pre wrap=""><a class="moz-txt-link-abbreviated" href="mailto:From:suporte@logicworks.pt">From:suporte@logicworks.pt</a> <a class="moz-txt-link-rfc2396E" href="mailto:suporte@logicworks.pt"><suporte@logicworks.pt></a> Sent: Sunday 17th March 2013 17:28 To: <a class="moz-txt-link-abbreviated" href="mailto:Users@ovirt.org">Users@ovirt.org</a> Subject: [Users] High Availability What should I need to configure to put HA working? I mean, when a host broke all the VM automatically move to another host. Do I need to have Power management enabled? Thanks _______________________________________________ Users mailing list <a class="moz-txt-link-abbreviated" href="mailto:Users@ovirt.org">Users@ovirt.org</a> <a class="moz-txt-link-freetext" href="http://lists.ovirt.org/mailman/listinfo/users">http://lists.ovirt.org/mailman/listinfo/users</a> </pre> </blockquote> <pre wrap="">_______________________________________________ Users mailing list <a class="moz-txt-link-abbreviated" href="mailto:Users@ovirt.org">Users@ovirt.org</a> <a class="moz-txt-link-freetext" href="http://lists.ovirt.org/mailman/listinfo/users">http://lists.ovirt.org/mailman/listinfo/users</a> </pre> </blockquote> <pre wrap=""> -- Dafna Ron _______________________________________________ Users mailing list <a class="moz-txt-link-abbreviated" href="mailto:Users@ovirt.org">Users@ovirt.org</a> <a class="moz-txt-link-freetext" href="http://lists.ovirt.org/mailman/listinfo/users">http://lists.ovirt.org/mailman/listinfo/users</a> </pre> </blockquote> <pre wrap="">_______________________________________________ Users mailing list <a class="moz-txt-link-abbreviated" href="mailto:Users@ovirt.org">Users@ovirt.org</a> <a class="moz-txt-link-freetext" href="http://lists.ovirt.org/mailman/listinfo/users">http://lists.ovirt.org/mailman/listinfo/users</a> </pre> </blockquote> <br> <br> <pre class="moz-signature" cols="72">-- --- 舒明 Shu Ming Open Virtualization Engineerning; CSTL, IBM Corp. Tel: 86-10-82451626 Tieline: 9051626 E-mail: <a class="moz-txt-link-abbreviated" href="mailto:shuming@cn.ibm.com">shuming@cn.ibm.com</a> or <a class="moz-txt-link-abbreviated" href="mailto:shuming@linux.vnet.ibm.com">shuming@linux.vnet.ibm.com</a> Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District, Beijing 100193, PRC</pre> </body> </html> --------------010000090502070605080205--
If one host is down because of network interrupt or power failure, the engine should know how many HA VMs are down and find out the VM images on the storage domain to start the VM instances on another host in the cluster. Why do we need power manager to be configured?
Power management allows the Manager to start highly available virtual machines on new hosts without worrying that virtual machine hard disk images will be corrupted. Imagine a situation in which the Manager cannot communicate with the host a highly available virtual machine is running on. If the host is still running as expected, and the virtual machine is also still running, the virtual machine is writing to its hard disk image. If the Manager starts that virtual machine on another host in the cluster, then both virtual machine instances will try and write to the disk image, and cause hard disk corruption. Power management lets the Manager be sure that only one instance of the highly available virtual machine is running, because the instance on the host the Manager couldn't communicate cannot survive a host reboot. Tim Hildred, RHCE Content Author II - Engineering Content Services, Red Hat, Inc. Brisbane, Australia Email: thildred@redhat.com Internal: 8588287 Mobile: +61 4 666 25242 IRC: thildred ----- Original Message -----
From: "Shu Ming" <shuming@linux.vnet.ibm.com> To: "Tim Hildred" <thildred@redhat.com> Cc: dron@redhat.com, Users@ovirt.org Sent: Monday, March 18, 2013 1:31:12 PM Subject: Re: [Users] High Availability
Tim,
Thanks for your information. I am not sure why we need power management to be configured for the hosts running HA virtual machines. We only need a method to check the VM or host status and a method to restart the VM instances with existing VM images on another host. Is it required to force powering down the failing host forever to make sure the failing host will not come back to live again?
* Power management must be configured for the hosts running the highly available virtual machines. * The host running the highly available virtual machine must be part of a cluster which has other available hosts. * The destination host must be running. * The source and destination host must have access to the data domain on which the virtual machine resides. * The source and destination host must have access to the same virtual networks and VLANs. * There must be enough CPUs on the destination host that are not in use to support the virtual machine's requirements. * There must be enough RAM on the destination host that is not in use to support the virtual machine's requirements.
Tim Hildred:
You might also find this helpful: https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Virtualiza... The topics before and after it explain a bit more about high availability.
Tim Hildred, RHCE Content Author II - Engineering Content Services, Red Hat, Inc. Brisbane, Australia Email: thildred@redhat.com Internal: 8588287 Mobile: +61 4 666 25242 IRC: thildred
----- Original Message -----
From: "Dafna Ron" <dron@redhat.com> To: suporte@logicworks.pt Cc: Users@ovirt.org Sent: Monday, March 18, 2013 4:46:51 AM Subject: Re: [Users] High Availability
I think that there is some confusion here so I will explain what are the configurations for fail-over.
power management will reboot your host if a connectivity issue is detected so all your vm's will be killed. resilience policy will allow you to choose vm migration policy during a host failure and its configured in the cluster level (clusters -> select cluster -> general sub tab -> edit policy) High Availability is configured only for servers type vm's and what it does is re-run the vm in case the pid of the vm is killed (so most commonly, if you have power management configured, and the host is rebooted, the vm will start automatically on a different host).
so it really depends what you want. if you want vm migration than look into cluster policy, if you want a specific vm to always be up and you don't care about the other vm's than configure power management and a HA vm. it really depends on what you need.
On 03/17/2013 07:15 PM, suporte@logicworks.pt wrote:
Is it Mandatory to have power manamement enabled? if yes what equipment do you recommend to use with it?
Regards Jose
----- Mensagem original ----- De: "René Koch" <r.koch@ovido.at> Para: suporte@logicworks.pt , Users@ovirt.org Enviadas: Domingo, 17 Março, 2013 16:47:41 Assunto: RE: [Users] High Availability
Hi,
You have to configure power management to make high availability working and mark the vms high availability checkbox...
Regards, René
-----Original message-----
From:suporte@logicworks.pt <suporte@logicworks.pt> Sent: Sunday 17th March 2013 17:28 To: Users@ovirt.org Subject: [Users] High Availability
What should I need to configure to put HA working? I mean, when a host broke all the VM automatically move to another host. Do I need to have Power management enabled?
Thanks _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users -- Dafna Ron _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
-- --- 舒明 Shu Ming Open Virtualization Engineerning; CSTL, IBM Corp. Tel: 86-10-82451626 Tieline: 9051626 E-mail: shuming@cn.ibm.com or shuming@linux.vnet.ibm.com Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District, Beijing 100193, PRC
Tim Hildred:
If one host is down because of network interrupt or power failure, the engine should know how many HA VMs are down and find out the VM images on the storage domain to start the VM instances on another host in the cluster. Why do we need power manager to be configured? Power management allows the Manager to start highly available virtual machines on new hosts without worrying that virtual machine hard disk images will be corrupted.
Imagine a situation in which the Manager cannot communicate with the host a highly available virtual machine is running on. If the host is still running as expected, and the virtual machine is also still running, the virtual machine is writing to its hard disk image. Tim,
Thanks for clarification. That is what I expected.
If the Manager starts that virtual machine on another host in the cluster, then both virtual machine instances will try and write to the disk image, and cause hard disk corruption.
Power management lets the Manager be sure that only one instance of the highly available virtual machine is running, because the instance on the host the Manager couldn't communicate cannot survive a host reboot.
Tim Hildred, RHCE Content Author II - Engineering Content Services, Red Hat, Inc. Brisbane, Australia Email: thildred@redhat.com Internal: 8588287 Mobile: +61 4 666 25242 IRC: thildred
----- Original Message -----
From: "Shu Ming" <shuming@linux.vnet.ibm.com> To: "Tim Hildred" <thildred@redhat.com> Cc: dron@redhat.com, Users@ovirt.org Sent: Monday, March 18, 2013 1:31:12 PM Subject: Re: [Users] High Availability
Tim,
Thanks for your information. I am not sure why we need power management to be configured for the hosts running HA virtual machines. We only need a method to check the VM or host status and a method to restart the VM instances with existing VM images on another host. Is it required to force powering down the failing host forever to make sure the failing host will not come back to live again?
* Power management must be configured for the hosts running the highly available virtual machines. * The host running the highly available virtual machine must be part of a cluster which has other available hosts. * The destination host must be running. * The source and destination host must have access to the data domain on which the virtual machine resides. * The source and destination host must have access to the same virtual networks and VLANs. * There must be enough CPUs on the destination host that are not in use to support the virtual machine's requirements. * There must be enough RAM on the destination host that is not in use to support the virtual machine's requirements.
Tim Hildred:
You might also find this helpful: https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Virtualiza... The topics before and after it explain a bit more about high availability.
Tim Hildred, RHCE Content Author II - Engineering Content Services, Red Hat, Inc. Brisbane, Australia Email: thildred@redhat.com Internal: 8588287 Mobile: +61 4 666 25242 IRC: thildred
----- Original Message -----
From: "Dafna Ron" <dron@redhat.com> To: suporte@logicworks.pt Cc: Users@ovirt.org Sent: Monday, March 18, 2013 4:46:51 AM Subject: Re: [Users] High Availability
I think that there is some confusion here so I will explain what are the configurations for fail-over.
power management will reboot your host if a connectivity issue is detected so all your vm's will be killed. resilience policy will allow you to choose vm migration policy during a host failure and its configured in the cluster level (clusters -> select cluster -> general sub tab -> edit policy) High Availability is configured only for servers type vm's and what it does is re-run the vm in case the pid of the vm is killed (so most commonly, if you have power management configured, and the host is rebooted, the vm will start automatically on a different host).
so it really depends what you want. if you want vm migration than look into cluster policy, if you want a specific vm to always be up and you don't care about the other vm's than configure power management and a HA vm. it really depends on what you need.
On 03/17/2013 07:15 PM, suporte@logicworks.pt wrote:
Is it Mandatory to have power manamement enabled? if yes what equipment do you recommend to use with it?
Regards Jose
----- Mensagem original ----- De: "René Koch" <r.koch@ovido.at> Para: suporte@logicworks.pt , Users@ovirt.org Enviadas: Domingo, 17 Março, 2013 16:47:41 Assunto: RE: [Users] High Availability
Hi,
You have to configure power management to make high availability working and mark the vms high availability checkbox...
Regards, René
-----Original message-----
From:suporte@logicworks.pt <suporte@logicworks.pt> Sent: Sunday 17th March 2013 17:28 To: Users@ovirt.org Subject: [Users] High Availability
What should I need to configure to put HA working? I mean, when a host broke all the VM automatically move to another host. Do I need to have Power management enabled?
Thanks _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users -- Dafna Ron _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
-- --- 舒明 Shu Ming Open Virtualization Engineerning; CSTL, IBM Corp. Tel: 86-10-82451626 Tieline: 9051626 E-mail: shuming@cn.ibm.com or shuming@linux.vnet.ibm.com Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District, Beijing 100193, PRC
-- --- 舒明 Shu Ming Open Virtualization Engineerning; CSTL, IBM Corp. Tel: 86-10-82451626 Tieline: 9051626 E-mail: shuming@cn.ibm.com or shuming@linux.vnet.ibm.com Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District, Beijing 100193, PRC
------=_Part_89_1367891.1363600245934 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Ok, now I understand, so what do we need to get the power management config= ured and working?=20 Regards=20 Jose=20 ----- Mensagem original ----- De: "Shu Ming" <shuming@linux.vnet.ibm.com>=20 Para: "Tim Hildred" <thildred@redhat.com>=20 Cc: Users@ovirt.org=20 Enviadas: Segunda-feira, 18 de Mar=C3=A7o de 2013 5:18:28=20 Assunto: Re: [Users] High Availability=20 Tim Hildred:=20
If one host is down because of network interrupt or power=20 failure, the engine should know how many HA VMs are down and find=20 out the VM images on the storage domain to start the VM instances on=20 another host in the cluster. Why do we need power manager to be=20 configured?=20 Power management allows the Manager to start highly available virtual mac= hines on new hosts without worrying that virtual machine hard disk images w= ill be corrupted.=20 =20 Imagine a situation in which the Manager cannot communicate with the host= a highly available virtual machine is running on. If the host is still run= ning as expected, and the virtual machine is also still running, the virtua= l machine is writing to its hard disk image.=20 Tim,=20
=20 If the Manager starts that virtual machine on another host in the cluster= , then both virtual machine instances will try and write to the disk image,= and cause hard disk corruption.=20 =20 Power management lets the Manager be sure that only one instance of the h= ighly available virtual machine is running, because the instance on the hos= t the Manager couldn't communicate cannot survive a host reboot.=20 =20 Tim Hildred, RHCE=20 Content Author II - Engineering Content Services, Red Hat, Inc.=20 Brisbane, Australia=20 Email: thildred@redhat.com=20 Internal: 8588287=20 Mobile: +61 4 666 25242=20 IRC: thildred=20 =20 ----- Original Message -----=20
From: "Shu Ming" <shuming@linux.vnet.ibm.com>=20 To: "Tim Hildred" <thildred@redhat.com>=20 Cc: dron@redhat.com, Users@ovirt.org=20 Sent: Monday, March 18, 2013 1:31:12 PM=20 Subject: Re: [Users] High Availability=20 =20 =20 Tim,=20 =20 Thanks for your information. I am not sure why we need power=20 management to be configured for the hosts running HA virtual=20 machines. We only need a method to check the VM or host status and=20 a method to restart the VM instances with existing VM images on=20 another host. Is it required to force powering down the failing host=20 forever to make sure the failing host will not come back to live=20 again?=20 =20 =20 =20 =20 *=20 Power management must be configured for the hosts running the highly=20 available virtual machines.=20 *=20 The host running the highly available virtual machine must be part of=20 a cluster which has other available hosts.=20 *=20 The destination host must be running.=20 *=20 The source and destination host must have access to the data domain=20 on which the virtual machine resides.=20 *=20 The source and destination host must have access to the same virtual=20 networks and VLANs.=20 *=20 There must be enough CPUs on the destination host that are not in use=20 to support the virtual machine's requirements.=20 *=20 There must be enough RAM on the destination host that is not in use=20 to support the virtual machine's requirements.=20 =20 =20 Tim Hildred:=20 =20 =20 You might also find this helpful:=20 https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Virtua=
Thanks for clarification. That is what I expected.=20 lization/3.1/html/Administration_Guide/High_availability_considerations.htm= l=20
The topics before and after it explain a bit more about high=20 availability.=20 =20 Tim Hildred, RHCE=20 Content Author II - Engineering Content Services, Red Hat, Inc.=20 Brisbane, Australia=20 Email: thildred@redhat.com Internal: 8588287=20 Mobile: +61 4 666 25242=20 IRC: thildred=20 =20 ----- Original Message -----=20 =20 From: "Dafna Ron" <dron@redhat.com> To: suporte@logicworks.pt Cc:=20 Users@ovirt.org Sent: Monday, March 18, 2013 4:46:51 AM=20 Subject: Re: [Users] High Availability=20 =20 I think that there is some confusion here so I will explain what are=20 the=20 configurations for fail-over.=20 =20 power management will reboot your host if a connectivity issue is=20 detected so all your vm's will be killed.=20 resilience policy will allow you to choose vm migration policy during=20 a=20 host failure and its configured in the cluster level (clusters ->=20 select=20 cluster -> general sub tab -> edit policy)=20 High Availability is configured only for servers type vm's and what=20 it=20 does is re-run the vm in case the pid of the vm is killed (so most=20 commonly, if you have power management configured, and the host is=20 rebooted, the vm will start automatically on a different host).=20 =20 so it really depends what you want. if you want vm migration than=20 look=20 into cluster policy, if you want a specific vm to always be up and=20 you=20 don't care about the other vm's than configure power management and a=20 HA=20 vm. it really depends on what you need.=20 =20 =20 =20 =20 On 03/17/2013 07:15 PM, suporte@logicworks.pt wrote:=20 =20 Is it Mandatory to have power manamement enabled? if yes what=20 equipment do you recommend to use with it?=20 =20 Regards=20 Jose=20 =20 =20 ----- Mensagem original -----=20 De: "Ren=C3=A9 Koch" <r.koch@ovido.at> Para: suporte@logicworks.pt ,=20 Users@ovirt.org Enviadas: Domingo, 17 Mar=C3=A7o, 2013 16:47:41=20 Assunto: RE: [Users] High Availability=20 =20 Hi,=20 =20 You have to configure power management to make high availability=20 working and mark the vms high availability checkbox...=20 =20 =20 Regards,=20 Ren=C3=A9=20 =20 =20 -----Original message-----=20 =20 From:suporte@logicworks.pt <suporte@logicworks.pt> Sent: Sunday 17th=20 March 2013 17:28=20 To: Users@ovirt.org Subject: [Users] High Availability=20 =20 What should I need to configure to put HA working? I mean, when a=20 host broke all the VM automatically move to another host.=20 Do I need to have Power management enabled?=20 =20 Thanks=20 _______________________________________________=20 Users mailing list Users@ovirt.org=20 http://lists.ovirt.org/mailman/listinfo/users=20 _______________________________________________=20 Users mailing list Users@ovirt.org=20 http://lists.ovirt.org/mailman/listinfo/users --=20 Dafna Ron=20 _______________________________________________=20 Users mailing list Users@ovirt.org=20 http://lists.ovirt.org/mailman/listinfo/users=20 _______________________________________________=20 Users mailing list Users@ovirt.org=20 http://lists.ovirt.org/mailman/listinfo/users=20 =20 --=20 ---=20 =E8=88=92=E6=98=8E Shu Ming=20 Open Virtualization Engineerning; CSTL, IBM Corp.=20 Tel: 86-10-82451626 Tieline: 9051626 E-mail: shuming@cn.ibm.com or=20 shuming@linux.vnet.ibm.com Address: 3/F Ring Building, ZhongGuanCun=20 Software Park, Haidian District, Beijing 100193, PRC=20
>> another host in the cluster. Why do we need power manager to be<b= r>>> configured?<br>> Power management allows the Manager to start= highly available virtual machines on new hosts without worrying that virtu= al machine hard disk images will be corrupted.<br>><br>> Imagine a si= tuation in which the Manager cannot communicate with the host a highly avai= lable virtual machine is running on. If the host is still running as expect= ed, and the virtual machine is also still running, the virtual machine is w= riting to its hard disk image.<br>Tim,<br><br>Thanks for clarification. Tha= t is what I expected.<br><br>><br>> If the Manager starts that virtua= l machine on another host in the cluster, then both virtual machine instanc= es will try and write to the disk image, and cause hard disk corruption.<br= ><br>> Power management lets the Manager be sure that only one insta= nce of the highly available virtual machine is running, because the instanc= e on the host the Manager couldn't communicate cannot survive a host reboot= .<br>><br>> Tim Hildred, RHCE<br>> Content Author II - Engineering= Content Services, Red Hat, Inc.<br>> Brisbane, Australia<br>> Email:=
>> Tim Hildred:<br>>><br>>><br>>> You might also f= ind this helpful:<br>>> https://access.redhat.com/knowledge/docs/en-U= S/Red_Hat_Enterprise_Virtualization/3.1/html/Administration_Guide/High_avai= lability_considerations.html<br>>> The topics before and after it exp= lain a bit more about high<br>>> availability.<br>>><br>>>= ; Tim Hildred, RHCE<br>>> Content Author II - Engineering Content Ser= vices, Red Hat, Inc.<br>>> Brisbane, Australia<br>>> Email: thi= ldred@redhat.com Internal: 8588287<br>>> Mobile: +61 4 666 25242<br>&= gt;> IRC: thildred<br>>><br>>> ----- Original Message -----<= br>>><br>>> From: "Dafna Ron" <dron@redhat.com> To: supor= te@logicworks.pt Cc:<br>>> Users@ovirt.org Sent: Monday, March 18, 20= 13 4:46:51 AM<br>>> Subject: Re: [Users] High Availability<br>>>= ;<br>>> I think that there is some confusion here so I will explain w= hat are<br>>> the<br>>> configurations for fail-over.<br>>&g= t;<br>>> power management will reboot your host if a connectivity iss= ue is<br>>> detected so all your vm's will be killed.<br>>> res= ilience policy will allow you to choose vm migration policy during<br>>&= gt; a<br>>> host failure and its configured in the cluster level (clu= sters -><br>>> select<br>>> cluster -> general sub tab -&= gt; edit policy)<br>>> High Availability is configured only for serve= rs type vm's and what<br>>> it<br>>> does is re-run the vm in c= ase the pid of the vm is killed (so most<br>>> commonly, if you have =
--=20 ---=20 =E8=88=92=E6=98=8E Shu Ming=20 Open Virtualization Engineerning; CSTL, IBM Corp.=20 Tel: 86-10-82451626 Tieline: 9051626 E-mail: shuming@cn.ibm.com or shuming@= linux.vnet.ibm.com=20 Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District, B= eijing 100193, PRC=20 _______________________________________________=20 Users mailing list=20 Users@ovirt.org=20 http://lists.ovirt.org/mailman/listinfo/users=20 ------=_Part_89_1367891.1363600245934 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable <html><head><style type=3D'text/css'>p { margin: 0; }</style></head><body><= div style=3D'font-family: verdana,helvetica,sans-serif; font-size: 10pt; co= lor: #330066'>Ok, now I understand, so what do we need to get the power man= agement configured and working?<br><br>Regards<br>Jose<br><br><hr id=3D"zwc= hr"><div style=3D"color: rgb(0, 0, 0); font-weight: normal; font-style: nor= mal; text-decoration: none; font-family: Helvetica,Arial,sans-serif; font-s= ize: 12pt;"><b>De: </b>"Shu Ming" <shuming@linux.vnet.ibm.com><br><b>= Para: </b>"Tim Hildred" <thildred@redhat.com><br><b>Cc: </b>Users@ovi= rt.org<br><b>Enviadas: </b>Segunda-feira, 18 de Mar=C3=A7o de 2013 5:18:28<= br><b>Assunto: </b>Re: [Users] High Availability<br><br>Tim Hildred:<br>>= ;> If one host is down because of network interrupt or power<br>>>= failure, the engine should know how many HA VMs are down and find<br>>&= gt; out the VM images on the storage domain to start the VM instances on<br= thildred@redhat.com<br>> Internal: 8588287<br>> Mobile: +61 4 666 25= 242<br>> IRC: thildred<br>><br>> ----- Original Message -----<br>&= gt;> From: "Shu Ming" <shuming@linux.vnet.ibm.com><br>>> To:= "Tim Hildred" <thildred@redhat.com><br>>> Cc: dron@redhat.com,= Users@ovirt.org<br>>> Sent: Monday, March 18, 2013 1:31:12 PM<br>>= ;> Subject: Re: [Users] High Availability<br>>><br>>><br>>= ;> Tim,<br>>><br>>> Thanks for your information. I am not su= re why we need power<br>>> management to be configured for the hosts = running HA virtual<br>>> machines. We only need a method to che= ck the VM or host status and<br>>> a method to restart the VM instanc= es with existing VM images on<br>>> another host. Is it required to f= orce powering down the failing host<br>>> forever to make sure the fa= iling host will not come back to live<br>>> again?<br>>><br>>= ;><br>>><br>>><br>>> *<br>>>= Power management must be configured for the hosts running the highly<br>&g= t;> available virtual machines.<br>>> *<br>>= ;> The host running the highly available virtual machine must be part of= <br>>> a cluster which has other available hosts.<br>>> = *<br>>> The destination host must be running.<br>>>= ; *<br>>> The source and destination host must ha= ve access to the data domain<br>>> on which the virtual machine resid= es.<br>>> *<br>>> The source and destinatio= n host must have access to the same virtual<br>>> networks and VLANs.= <br>>> *<br>>> There must be enough CPUs on= the destination host that are not in use<br>>> to support the virtua= l machine's requirements.<br>>> *<br>>> The= re must be enough RAM on the destination host that is not in use<br>>>= ; to support the virtual machine's requirements.<br>>><br>>><br= power management configured, and the host is<br>>> rebooted, the vm w= ill start automatically on a different host).<br>>><br>>> so it= really depends what you want. if you want vm migration than<br>>> lo= ok<br>>> into cluster policy, if you want a specific vm to always be = up and<br>>> you<br>>> don't care about the other vm's than con= figure power management and a<br>>> HA<br>>> vm. it really depe= nds on what you need.<br>>><br>>><br>>><br>>><br>&g= t;> On 03/17/2013 07:15 PM, suporte@logicworks.pt wrote:<br>>><br>= >> Is it Mandatory to have power manamement enabled? if yes what<br>&= gt;> equipment do you recommend to use with it?<br>>><br>>> = Regards<br>>> Jose<br>>><br>>><br>>> ----- Mensagem= original -----<br>>> De: "Ren=C3=A9 Koch" <r.koch@ovido.at> Pa= ra: suporte@logicworks.pt ,<br>>> Users@ovirt.org Enviadas: Domingo, = 17 Mar=C3=A7o, 2013 16:47:41<br>>> Assunto: RE: [Users] High Availabi= lity<br>>><br>>> Hi,<br>>><br>>> You have to config= ure power management to make high availability<br>>> working and mark= the vms high availability checkbox...<br>>><br>>><br>>> = Regards,<br>>> Ren=C3=A9<br>>> <br>>> <br>&= gt;> -----Original message-----<br>>><br>>> From:suporte@log= icworks.pt <suporte@logicworks.pt> Sent: Sunday 17th<br>>> Marc= h 2013 17:28<br>>> To: Users@ovirt.org Subject: [Users] High Availabi= lity<br>>><br>>> What should I need to configure to put HA work= ing? I mean, when a<br>>> host broke all the VM automatically move to= another host.<br>>> Do I need to have Power management enabled?<br>&= gt;><br>>> Thanks<br>>> ____________________________________= ___________<br>>> Users mailing list Users@ovirt.org<br>>> http= ://lists.ovirt.org/mailman/listinfo/users<br>>> _____________________= __________________________<br>>> Users mailing list Users@ovirt.org<b= r>>> http://lists.ovirt.org/mailman/listinfo/users --<br>>> Daf= na Ron<br>>> _______________________________________________<br>>&= gt; Users mailing list Users@ovirt.org<br>>> http://lists.ovirt.org/m= ailman/listinfo/users<br>>> _________________________________________= ______<br>>> Users mailing list Users@ovirt.org<br>>> http://li= sts.ovirt.org/mailman/listinfo/users<br>>><br>>> --<br>>>= ---<br>>> =E8=88=92=E6=98=8E Shu Ming<br>>> Open Virtualizatio= n Engineerning; CSTL, IBM Corp.<br>>> Tel: 86-10-82451626 Tieli= ne: 9051626 E-mail: shuming@cn.ibm.com or<br>>> shuming@linux.vnet.ib= m.com Address: 3/F Ring Building, ZhongGuanCun<br>>> Software Park, H= aidian District, Beijing 100193, PRC<br><br><br>-- <br>---<br>=E8=88=92=E6= =98=8E Shu Ming<br>Open Virtualization Engineerning; CSTL, IBM Corp.<br>Tel= : 86-10-82451626 Tieline: 9051626 E-mail: shuming@cn.ibm.com or shumi= ng@linux.vnet.ibm.com<br>Address: 3/F Ring Building, ZhongGuanCun Software = Park, Haidian District, Beijing 100193, PRC<br><br><br>____________________= ___________________________<br>Users mailing list<br>Users@ovirt.org<br>htt= p://lists.ovirt.org/mailman/listinfo/users<br></div><br></div></body></html=
------=_Part_89_1367891.1363600245934--
On Mon, 2013-03-18 at 09:50 +0000, suporte@logicworks.pt wrote:
Ok, now I understand, so what do we need to get the power management configured and working?
You need a remote management interface (IPMI, ILO,...) in your servers and an user which has permissions to power off/on/reset the server using this interface. The IP address of this interface must be accessible from all hosts in your cluster. When editing your host preferences you see all supported devices under "Power Management" - "Type". On most systems (IBM, hp, Supermicro,...) ipmilan will work. Btw, does anyone know if it's possible to add custom fencing scripts for power management? Regards, René
Regards Jose
______________________________________________________________________ De: "Shu Ming" <shuming@linux.vnet.ibm.com> Para: "Tim Hildred" <thildred@redhat.com> Cc: Users@ovirt.org Enviadas: Segunda-feira, 18 de Março de 2013 5:18:28 Assunto: Re: [Users] High Availability
Tim Hildred:
If one host is down because of network interrupt or power failure, the engine should know how many HA VMs are down and find out the VM images on the storage domain to start the VM instances on another host in the cluster. Why do we need power manager to be configured? Power management allows the Manager to start highly available virtual machines on new hosts without worrying that virtual machine hard disk images will be corrupted.
Imagine a situation in which the Manager cannot communicate with the host a highly available virtual machine is running on. If the host is still running as expected, and the virtual machine is also still running, the virtual machine is writing to its hard disk image. Tim,
Thanks for clarification. That is what I expected.
If the Manager starts that virtual machine on another host in the
cluster, then both virtual machine instances will try and write to the disk image, and cause hard disk corruption.
Power management lets the Manager be sure that only one instance of
the highly available virtual machine is running, because the instance on the host the Manager couldn't communicate cannot survive a host reboot.
Tim Hildred, RHCE Content Author II - Engineering Content Services, Red Hat, Inc. Brisbane, Australia Email: thildred@redhat.com Internal: 8588287 Mobile: +61 4 666 25242 IRC: thildred
----- Original Message -----
From: "Shu Ming" <shuming@linux.vnet.ibm.com> To: "Tim Hildred" <thildred@redhat.com> Cc: dron@redhat.com, Users@ovirt.org Sent: Monday, March 18, 2013 1:31:12 PM Subject: Re: [Users] High Availability
Tim,
Thanks for your information. I am not sure why we need power management to be configured for the hosts running HA virtual machines. We only need a method to check the VM or host status and a method to restart the VM instances with existing VM images on another host. Is it required to force powering down the failing
host
forever to make sure the failing host will not come back to live again?
* Power management must be configured for the hosts running the highly available virtual machines. * The host running the highly available virtual machine must be part of a cluster which has other available hosts. * The destination host must be running. * The source and destination host must have access to the data domain on which the virtual machine resides. * The source and destination host must have access to the same virtual networks and VLANs. * There must be enough CPUs on the destination host that are not in use to support the virtual machine's requirements. * There must be enough RAM on the destination host that is not in use to support the virtual machine's requirements.
Tim Hildred:
You might also find this helpful:
https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Virtualiza...
The topics before and after it explain a bit more about high availability.
Tim Hildred, RHCE Content Author II - Engineering Content Services, Red Hat, Inc. Brisbane, Australia Email: thildred@redhat.com Internal: 8588287 Mobile: +61 4 666 25242 IRC: thildred
----- Original Message -----
From: "Dafna Ron" <dron@redhat.com> To: suporte@logicworks.pt Cc: Users@ovirt.org Sent: Monday, March 18, 2013 4:46:51 AM Subject: Re: [Users] High Availability
I think that there is some confusion here so I will explain what are the configurations for fail-over.
power management will reboot your host if a connectivity issue is detected so all your vm's will be killed. resilience policy will allow you to choose vm migration policy during a host failure and its configured in the cluster level (clusters -> select cluster -> general sub tab -> edit policy) High Availability is configured only for servers type vm's and what it does is re-run the vm in case the pid of the vm is killed (so most commonly, if you have power management configured, and the host is rebooted, the vm will start automatically on a different host).
so it really depends what you want. if you want vm migration than look into cluster policy, if you want a specific vm to always be up and you don't care about the other vm's than configure power management and a HA vm. it really depends on what you need.
On 03/17/2013 07:15 PM, suporte@logicworks.pt wrote:
Is it Mandatory to have power manamement enabled? if yes what equipment do you recommend to use with it?
Regards Jose
----- Mensagem original ----- De: "René Koch" <r.koch@ovido.at> Para: suporte@logicworks.pt , Users@ovirt.org Enviadas: Domingo, 17 Março, 2013 16:47:41 Assunto: RE: [Users] High Availability
Hi,
You have to configure power management to make high availability working and mark the vms high availability checkbox...
Regards, René
-----Original message-----
From:suporte@logicworks.pt <suporte@logicworks.pt> Sent: Sunday 17th March 2013 17:28 To: Users@ovirt.org Subject: [Users] High Availability
What should I need to configure to put HA working? I mean, when a host broke all the VM automatically move to another host. Do I need to have Power management enabled?
Thanks _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users -- Dafna Ron _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
-- --- 舒明 Shu Ming Open Virtualization Engineerning; CSTL, IBM Corp. Tel: 86-10-82451626 Tieline: 9051626 E-mail: shuming@cn.ibm.com or shuming@linux.vnet.ibm.com Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District, Beijing 100193, PRC
-- --- 舒明 Shu Ming Open Virtualization Engineerning; CSTL, IBM Corp. Tel: 86-10-82451626 Tieline: 9051626 E-mail: shuming@cn.ibm.com or shuming@linux.vnet.ibm.com Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District, Beijing 100193, PRC
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Hi, We have 2 Fujitsu servers and one iSCSI storage domain. The servers have the power management configured with ilo3. We can live migrate a VM and when rebooting the host of that VM it does the migration to the other host. For testing high availability we disconnected all NIC cables of the VM host, the VM does not migrate to the other host, we had to manually confirm the host has been rebooted, and than migration happens. Is this the correct behavior? We have to manually confirm that the host has been rebooted for HA happens? Regards Jose ----- Mensagem original ----- De: "René Koch (ovido)" <r.koch@ovido.at> Para: suporte@logicworks.pt Cc: "Shu Ming" <shuming@linux.vnet.ibm.com>, Users@ovirt.org Enviadas: Segunda-feira, 18 Março, 2013 10:03:01 Assunto: Re: [Users] High Availability On Mon, 2013-03-18 at 09:50 +0000, suporte@logicworks.pt wrote:
Ok, now I understand, so what do we need to get the power management configured and working?
You need a remote management interface (IPMI, ILO,...) in your servers and an user which has permissions to power off/on/reset the server using this interface. The IP address of this interface must be accessible from all hosts in your cluster. When editing your host preferences you see all supported devices under "Power Management" - "Type". On most systems (IBM, hp, Supermicro,...) ipmilan will work. Btw, does anyone know if it's possible to add custom fencing scripts for power management? Regards, René
Regards Jose
______________________________________________________________________ De: "Shu Ming" <shuming@linux.vnet.ibm.com> Para: "Tim Hildred" <thildred@redhat.com> Cc: Users@ovirt.org Enviadas: Segunda-feira, 18 de Março de 2013 5:18:28 Assunto: Re: [Users] High Availability
Tim Hildred:
If one host is down because of network interrupt or power failure, the engine should know how many HA VMs are down and find out the VM images on the storage domain to start the VM instances on another host in the cluster. Why do we need power manager to be configured? Power management allows the Manager to start highly available virtual machines on new hosts without worrying that virtual machine hard disk images will be corrupted.
Imagine a situation in which the Manager cannot communicate with the host a highly available virtual machine is running on. If the host is still running as expected, and the virtual machine is also still running, the virtual machine is writing to its hard disk image. Tim,
Thanks for clarification. That is what I expected.
If the Manager starts that virtual machine on another host in the
cluster, then both virtual machine instances will try and write to the disk image, and cause hard disk corruption.
Power management lets the Manager be sure that only one instance of
the highly available virtual machine is running, because the instance on the host the Manager couldn't communicate cannot survive a host reboot.
Tim Hildred, RHCE Content Author II - Engineering Content Services, Red Hat, Inc. Brisbane, Australia Email: thildred@redhat.com Internal: 8588287 Mobile: +61 4 666 25242 IRC: thildred
----- Original Message -----
From: "Shu Ming" <shuming@linux.vnet.ibm.com> To: "Tim Hildred" <thildred@redhat.com> Cc: dron@redhat.com, Users@ovirt.org Sent: Monday, March 18, 2013 1:31:12 PM Subject: Re: [Users] High Availability
Tim,
Thanks for your information. I am not sure why we need power management to be configured for the hosts running HA virtual machines. We only need a method to check the VM or host status and a method to restart the VM instances with existing VM images on another host. Is it required to force powering down the failing
host
forever to make sure the failing host will not come back to live again?
* Power management must be configured for the hosts running the highly available virtual machines. * The host running the highly available virtual machine must be part of a cluster which has other available hosts. * The destination host must be running. * The source and destination host must have access to the data domain on which the virtual machine resides. * The source and destination host must have access to the same virtual networks and VLANs. * There must be enough CPUs on the destination host that are not in use to support the virtual machine's requirements. * There must be enough RAM on the destination host that is not in use to support the virtual machine's requirements.
Tim Hildred:
You might also find this helpful:
https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Virtualiza...
The topics before and after it explain a bit more about high availability.
Tim Hildred, RHCE Content Author II - Engineering Content Services, Red Hat, Inc. Brisbane, Australia Email: thildred@redhat.com Internal: 8588287 Mobile: +61 4 666 25242 IRC: thildred
----- Original Message -----
From: "Dafna Ron" <dron@redhat.com> To: suporte@logicworks.pt Cc: Users@ovirt.org Sent: Monday, March 18, 2013 4:46:51 AM Subject: Re: [Users] High Availability
I think that there is some confusion here so I will explain what are the configurations for fail-over.
power management will reboot your host if a connectivity issue is detected so all your vm's will be killed. resilience policy will allow you to choose vm migration policy during a host failure and its configured in the cluster level (clusters -> select cluster -> general sub tab -> edit policy) High Availability is configured only for servers type vm's and what it does is re-run the vm in case the pid of the vm is killed (so most commonly, if you have power management configured, and the host is rebooted, the vm will start automatically on a different host).
so it really depends what you want. if you want vm migration than look into cluster policy, if you want a specific vm to always be up and you don't care about the other vm's than configure power management and a HA vm. it really depends on what you need.
On 03/17/2013 07:15 PM, suporte@logicworks.pt wrote:
Is it Mandatory to have power manamement enabled? if yes what equipment do you recommend to use with it?
Regards Jose
----- Mensagem original ----- De: "René Koch" <r.koch@ovido.at> Para: suporte@logicworks.pt , Users@ovirt.org Enviadas: Domingo, 17 Março, 2013 16:47:41 Assunto: RE: [Users] High Availability
Hi,
You have to configure power management to make high availability working and mark the vms high availability checkbox...
Regards, René
-----Original message-----
From:suporte@logicworks.pt <suporte@logicworks.pt> Sent: Sunday 17th March 2013 17:28 To: Users@ovirt.org Subject: [Users] High Availability
What should I need to configure to put HA working? I mean, when a host broke all the VM automatically move to another host. Do I need to have Power management enabled?
Thanks _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users -- Dafna Ron _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
-- --- 舒明 Shu Ming Open Virtualization Engineerning; CSTL, IBM Corp. Tel: 86-10-82451626 Tieline: 9051626 E-mail: shuming@cn.ibm.com or shuming@linux.vnet.ibm.com Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District, Beijing 100193, PRC
-- --- 舒明 Shu Ming Open Virtualization Engineerning; CSTL, IBM Corp. Tel: 86-10-82451626 Tieline: 9051626 E-mail: shuming@cn.ibm.com or shuming@linux.vnet.ibm.com Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District, Beijing 100193, PRC
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
On Tue, Apr 16, 2013 at 12:56 PM, suporte wrote:
Hi,
We have 2 Fujitsu servers and one iSCSI storage domain. The servers have the power management configured with ilo3. We can live migrate a VM and when rebooting the host of that VM it does the migration to the other host.
For testing high availability we disconnected all NIC cables of the VM host, the VM does not migrate to the other host, we had to manually confirm the host has been rebooted, and than migration happens.
Is this the correct behavior? We have to manually confirm that the host has been rebooted for HA happens?
Regards Jose
Hello, when you say "we disconnected all NIC cables" you mean "we disconnected all NIC cables but the ones connected to the iLO interface", correct? Because to know that one host has successfully fenced the problematic one, it has to send a get status message and see that it is off or that it has been successfully rebooted..... For esxample in RHCS if you configure iLO as a fencing device it remains indefinitely in state similar to wait for fence to complete if the "fencer" is not able to get an acknowledge about the operation or to reach the other node iLO. Probably you can find something in your logs... Gianluca
Well, we also disconnected the ilo NIC cable. We did another test, and just disconnected the NIC cables but the ilo NIC cable, and voilá the HA took about 3 minutes to migrate the VM to the other host. We notice too that the manager did a reboot to the failed host. For a more real scenario we disconnected the power cable from the host and after about 2 or 3 minutes the manager put the host in non-responsive and the VM in unknown state. Is this the correct behavior? Regards Jose ----- Mensagem original ----- De: "Gianluca Cecchi" <gianluca.cecchi@gmail.com> Para: suporte@logicworks.pt Cc: "René Koch (ovido)" <r.koch@ovido.at>, "users" <Users@ovirt.org> Enviadas: Terça-feira, 16 Abril, 2013 12:12:43 Assunto: Re: [Users] High Availability On Tue, Apr 16, 2013 at 12:56 PM, suporte wrote:
Hi,
We have 2 Fujitsu servers and one iSCSI storage domain. The servers have the power management configured with ilo3. We can live migrate a VM and when rebooting the host of that VM it does the migration to the other host.
For testing high availability we disconnected all NIC cables of the VM host, the VM does not migrate to the other host, we had to manually confirm the host has been rebooted, and than migration happens.
Is this the correct behavior? We have to manually confirm that the host has been rebooted for HA happens?
Regards Jose
Hello, when you say "we disconnected all NIC cables" you mean "we disconnected all NIC cables but the ones connected to the iLO interface", correct? Because to know that one host has successfully fenced the problematic one, it has to send a get status message and see that it is off or that it has been successfully rebooted..... For esxample in RHCS if you configure iLO as a fencing device it remains indefinitely in state similar to wait for fence to complete if the "fencer" is not able to get an acknowledge about the operation or to reach the other node iLO. Probably you can find something in your logs... Gianluca
On Tue, Apr 16, 2013 at 2:03 PM, suporte wrote:
Well, we also disconnected the ilo NIC cable. We did another test, and just disconnected the NIC cables but the ilo NIC cable, and voilá the HA took about 3 minutes to migrate the VM to the other host. We notice too that the manager did a reboot to the failed host. For a more real scenario we disconnected the power cable from the host and after about 2 or 3 minutes the manager put the host in non-responsive and the VM in unknown state. Is this the correct behavior?
Just to confirm your environment right now: - what is the resilience policy of your cluster at the moment? cluster -> edit -> resilience policy - what is the high availability settings for the particular VMs you are testing in this cluster? Gianluca
-----Original message-----
From:suporte@logicworks.pt <suporte@logicworks.pt> Sent: Tuesday 16th April 2013 14:03 To: Gianluca Cecchi <gianluca.cecchi@gmail.com> Cc: René Koch <r.koch@ovido.at>; users <Users@ovirt.org> Subject: Re: [Users] High Availability
Well, we also disconnected the ilo NIC cable. We did another test, and just disconnected the NIC cables but the ilo NIC cable, and voilá the HA took about 3 minutes to migrate the VM to the other host. We notice too that the manager did a reboot to the failed host. For a more real scenario we disconnected the power cable from the host and after about 2 or 3 minutes the manager put the host in non-responsive and the VM in unknown state. Is this the correct behavior?
Fencing means that the non-responsive host gets reseted (powered off and on). If fencing isn't working (as you disconnected the power cable and so ILO can't send you a success message) the vms want get started on another host. In your example this seems to be strange, but lets have a look at the following scenario: - You have 2 datacenters with 1 hypervisor in DC 1 and 1 hypervisor in DC 2, ovirt-engine is running in DC 1 - Connection between dcs is lost - Fencing isn't working - VM is running on host in DC 2 - If VM would start on host in DC 1 without successful fencing your vm disk would be broken (host in DC 2 and DC 1 is writing on the same storage file) Maybe there are better examples then this one (would be interesting to know what your storage metro-cluster is doing in this scenario with this split-brain-situation), but I hope it's clear to you why fencing is working as it is and what can happen if it would be less restrictive... Regards, René
Regards Jose
----- Mensagem original ----- De: "Gianluca Cecchi" <gianluca.cecchi@gmail.com> Para: suporte@logicworks.pt Cc: "René Koch (ovido)" <r.koch@ovido.at>, "users" <Users@ovirt.org> Enviadas: Terça-feira, 16 Abril, 2013 12:12:43 Assunto: Re: [Users] High Availability
On Tue, Apr 16, 2013 at 12:56 PM, suporte wrote:
Hi,
We have 2 Fujitsu servers and one iSCSI storage domain. The servers have the power management configured with ilo3. We can live migrate a VM and when rebooting the host of that VM it does the migration to the other host.
For testing high availability we disconnected all NIC cables of the VM host, the VM does not migrate to the other host, we had to manually confirm the host has been rebooted, and than migration happens.
Is this the correct behavior? We have to manually confirm that the host has been rebooted for HA happens?
Regards Jose
Hello, when you say "we disconnected all NIC cables" you mean "we disconnected all NIC cables but the ones connected to the iLO interface", correct? Because to know that one host has successfully fenced the problematic one, it has to send a get status message and see that it is off or that it has been successfully rebooted.....
For esxample in RHCS if you configure iLO as a fencing device it remains indefinitely in state similar to
wait for fence to complete
if the "fencer" is not able to get an acknowledge about the operation or to reach the other node iLO. Probably you can find something in your logs...
Gianluca
From:suporte@logicworks.pt <suporte@logicworks.pt>=20 Sent: Tuesday 16th April 2013 14:03=20 To: Gianluca Cecchi <gianluca.cecchi@gmail.com>=20 Cc: Ren=C3=A9 Koch <r.koch@ovido.at>; users <Users@ovirt.org>=20 Subject: Re: [Users] High Availability=20 =20 Well, we also disconnected the ilo NIC cable. We did another test, and ju= st disconnected the NIC cables but the ilo NIC cable, and voil=C3=A1 the HA= took about 3 minutes to migrate the VM to the other host. We notice too th= at the manager did a reboot to the failed host. For a more real scenario we= disconnected the power cable from the host and after about 2 or 3 minutes =
=20 Regards=20 Jose=20 =20 ----- Mensagem original -----=20 De: "Gianluca Cecchi" <gianluca.cecchi@gmail.com>=20 Para: suporte@logicworks.pt=20 Cc: "Ren=C3=A9 Koch (ovido)" <r.koch@ovido.at>, "users" <Users@ovirt.org>= =20 Enviadas: Ter=C3=A7a-feira, 16 Abril, 2013 12:12:43=20 Assunto: Re: [Users] High Availability=20 =20 On Tue, Apr 16, 2013 at 12:56 PM, suporte wrote:=20
Hi,=20 =20 We have 2 Fujitsu servers and one iSCSI storage domain. The servers hav= e the power management configured with ilo3.=20 We can live migrate a VM and when rebooting the host of that VM it does=
=20 For testing high availability we disconnected all NIC cables of the VM = host, the VM does not migrate to the other host, we had to manually confirm=
------=_Part_29483_11651952.1366120165705 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Yes, fencing must be working otherwise HA does not work. So in the case of = a power supply failure we have to have a server with a redundant power supp= ly to previse this scenario?=20 ----- Original Message ----- From: "Ren=C3=A9 Koch" <r.koch@ovido.at>=20 To: suporte@logicworks.pt, "Gianluca Cecchi" <gianluca.cecchi@gmail.com>=20 Cc: "users" <Users@ovirt.org>=20 Sent: Ter=C3=A7a-feira, 16 de Abril de 2013 13:31:48=20 Subject: RE: [Users] High Availability=20 -----Original message-----=20 the manager put the host in non-responsive and the VM in unknown state. Is = this the correct behavior?=20 Fencing means that the non-responsive host gets reseted (powered off and on= ).=20 If fencing isn't working (as you disconnected the power cable and so ILO ca= n't send you a success message) the vms want get started on another host.= =20 In your example this seems to be strange, but lets have a look at the follo= wing scenario:=20 - You have 2 datacenters with 1 hypervisor in DC 1 and 1 hypervisor in DC 2= , ovirt-engine is running in DC 1=20 - Connection between dcs is lost=20 - Fencing isn't working=20 - VM is running on host in DC 2=20 - If VM would start on host in DC 1 without successful fencing your vm disk= would be broken (host in DC 2 and DC 1 is writing on the same storage file= )=20 Maybe there are better examples then this one (would be interesting to know= what your storage metro-cluster is doing in this scenario with this split-= brain-situation), but I hope it's clear to you why fencing is working as it= is and what can happen if it would be less restrictive...=20 Regards,=20 Ren=C3=A9=20 the migration to the other host.=20 the host has been rebooted, and than migration happens.=20
=20 Is this the correct behavior? We have to manually confirm that the host= has been rebooted for HA happens?=20 =20 Regards=20 Jose=20 =20 Hello,=20 when you say "we disconnected all NIC cables" you mean "we=20 disconnected all NIC cables but the ones connected to the iLO=20 interface", correct?=20 Because to know that one host has successfully fenced the problematic=20 one, it has to send a get status message and see that it is off or=20 that it has been successfully rebooted.....=20 =20 For esxample in RHCS if you configure iLO as a fencing device it=20 remains indefinitely in state similar to=20 =20 wait for fence to complete=20 =20 if the "fencer" is not able to get an acknowledge about the operation=20 or to reach the other node iLO.=20 Probably you can find something in your logs...=20 =20 Gianluca=20 =20
From: </b>"Ren=C3=A9 Koch" <r.koch@ovido.at><br><b>To: </b>suporte@l= ogicworks.pt, "Gianluca Cecchi" <gianluca.cecchi@gmail.com><br><b>Cc:= </b>"users" <Users@ovirt.org><br><b>Sent: </b>Ter=C3=A7a-feira, 16 d= e Abril de 2013 13:31:48<br><b>Subject: </b>RE: [Users] High Availability<b= r><br><br> <br>-----Original message-----<br>> From:suporte@logicwo= rks.pt <suporte@logicworks.pt><br>> Sent: Tuesday 16th April 2013 = 14:03<br>> To: Gianluca Cecchi <gianluca.cecchi@gmail.com><br>>= Cc: Ren=C3=A9 Koch <r.koch@ovido.at>; users <Users@ovirt.org><= br>> Subject: Re: [Users] High Availability<br>> <br>> Well, we al= so disconnected the ilo NIC cable. We did another test, and just disconnect= ed the NIC cables but the ilo NIC cable, and voil=C3=A1 the HA took about 3= minutes to migrate the VM to the other host. We notice too that the manage= r did a reboot to the failed host. For a more real scenario we disconnected=
- VM is running on host in DC 2<br>- If VM would start on host in DC 1 wit= hout successful fencing your vm disk would be broken (host in DC 2 and DC 1= is writing on the same storage file)<br><br>Maybe there are better example= s then this one (would be interesting to know what your storage metro-clust= er is doing in this scenario with this split-brain-situation), but I hope i= t's clear to you why fencing is working as it is and what can happen if it = would be less restrictive...<br><br><br>Regards,<br>Ren=C3=A9<br><br><br>&g= t; <br>> Regards<br>> Jose<br>> <br>> ----- Mensagem original -= ----<br>> De: "Gianluca Cecchi" <gianluca.cecchi@gmail.com><br>>= ; Para: suporte@logicworks.pt<br>> Cc: "Ren=C3=A9 Koch (ovido)" <r.ko= ch@ovido.at>, "users" <Users@ovirt.org><br>> Enviadas: Ter=C3= =A7a-feira, 16 Abril, 2013 12:12:43<br>> Assunto: Re: [Users] High Avail= ability<br>> <br>> On Tue, Apr 16, 2013 at 12:56 PM, suporte wr= ote:<br>> > Hi,<br>> ><br>> > We have 2 Fujitsu servers a= nd one iSCSI storage domain. The servers have the power management configur= ed with ilo3.<br>> > We can live migrate a VM and when rebooting the = host of that VM it does the migration to the other host.<br>> ><br>&g= t; > For testing high availability we disconnected all NIC cables of the= VM host, the VM does not migrate to the other host, we had to manually con= firm the host has been rebooted, and than migration happens.<br>> ><b= r>> > Is this the correct behavior? We have to manually confirm that =
------=_Part_29483_11651952.1366120165705 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable <html><head><style type=3D'text/css'>p { margin: 0; }</style></head><body><= div style=3D'font-family: arial,helvetica,sans-serif; font-size: 10pt; colo= r: #000000'>Yes, fencing must be working otherwise HA does not work. So in = the case of a power supply failure we have to have a server with a redundan= t power supply to previse this scenario?<br><br><hr id=3D"zwchr"><div style= =3D"color: rgb(0, 0, 0); font-weight: normal; font-style: normal; text-deco= ration: none; font-family: Helvetica,Arial,sans-serif; font-size: 12pt;"><b= the power cable from the host and after about 2 or 3 minutes the manager p= ut the host in non-responsive and the VM in unknown state. Is this the corr= ect behavior?<br><br><br>Fencing means that the non-responsive host gets re= seted (powered off and on).<br>If fencing isn't working (as you disconnecte= d the power cable and so ILO can't send you a success message) the vms want= get started on another host.<br>In your example this seems to be strange, = but lets have a look at the following scenario:<br>- You have 2 datacenters= with 1 hypervisor in DC 1 and 1 hypervisor in DC 2, ovirt-engine is runnin= g in DC 1<br>- Connection between dcs is lost<br>- Fencing isn't working<br= the host has been rebooted for HA happens?<br>> ><br>> > Regard= s<br>> > Jose<br>> <br>> Hello,<br>> when you say "we discon= nected all NIC cables" you mean "we<br>> disconnected all NIC cables but= the ones connected to the iLO<br>> interface", correct?<br>> Because= to know that one host has successfully fenced the problematic<br>> one,= it has to send a get status message and see that it is off or<br>> that= it has been successfully rebooted.....<br>> <br>> For esxample in RH= CS if you configure iLO as a fencing device it<br>> remains indefinitely= in state similar to<br>> <br>> wait for fence to complete<br>> <b= r>> if the "fencer" is not able to get an acknowledge about the operatio= n<br>> or to reach the other node iLO.<br>> Probably you can find som= ething in your logs...<br>> <br>> Gianluca<br>> <br></div><br></di= v></body></html> ------=_Part_29483_11651952.1366120165705--
participants (8)
-
Dafna Ron -
Gianluca Cecchi -
Noam Slomianko -
René Koch -
René Koch (ovido)
-
Shu Ming -
suporte＠logicworks.pt -
Tim Hildred