[ovirt-users] High availability when both engine host and host with application vm failed

[Sergei Hanus]

I want to make a setup, when workload is distributed between two sites are
high availability mechanism protects from one site failure, restarting vms
on another site.

Scenario I use:
1. Poweroff hosted engine host, and then host with highly-available vm
2. Engine comes back on another site (which is fine).
3. What I expect, engine finds, that there's a host not available with HA
vms, and restart these vms on another host. But, I only see in logs, that
engine reports, that it cannot connect to that host
(java.net.NoRouteToHostException: No route to host).

Whel I poweroff just server with app vm, High Availability works correctly,
performs fencing and restarts vm on another host.

I use release 4.1 from RedHat.

Has anyone faced similar issue? And, if yes, how could that be
toubleshooted?

 Thank you in advance,

Sergei.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] High Availability Setup with oVirt

[Yaniv Kaul]

On Tue, Aug 15, 2017 at 6:25 AM, Anantha Raghava <
rag...@exzatechconsulting.com> wrote:

> Hi,
>
> I am trying to setup ovirt clusters in two different locations and
> replicate the data between two sites so that in case of failure in primary
> site, I can bring the VM up in secondary site in quick time with minimum
> data loss. Can we do this oVirt?
>
> I was thinking of using DRBD, however read somewhere that oVirt plugins
> are still under development
>

How about Gluster geo-replication?
Y.


> --
>
> Thanks & Regards,
>
>
> Anantha Raghava
>
> Do not print this e-mail unless required. Save Paper & trees.
>
> ___
> 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

[ovirt-users] High Availability Setup with oVirt

[Anantha Raghava]

Hi,

I am trying to setup ovirt clusters in two different locations and 
replicate the data between two sites so that in case of failure in 
primary site, I can bring the VM up in secondary site in quick time with 
minimum data loss. Can we do this oVirt?


I was thinking of using DRBD, however read somewhere that oVirt plugins 
are still under development


--

Thanks & Regards,


Anantha Raghava


Do not print this e-mail unless required. Save Paper & trees.

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] high availability

[Nir Soffer]

On Fri, Feb 3, 2017 at 9:49 PM, Yaniv Kaul  wrote:
>
>
> On Fri, Feb 3, 2017 at 8:42 PM, cmc  wrote:
>>
>> Hi,
>>
>> I have some questions about oVirt's high availability features for
>> VMs. My understanding is that it relies on the engine host to monitor
>> and manage the hypervisor hosts, so that in the case of a
>> unrecoverable failure of one those hosts, it will fence the host and
>> migrate any VM that is designated as highly available to another host
>> in the cluster. However, if the engine is itself hosted as a VM on a
>> host that fails, this process cannot take place, as the engine will be
>> down and cannot initiate monitoring, fencing and migration - is that
>> correct?
>
>
> The hosted-engine has its own HA mechanism.

You may find this useful:
http://www.ovirt.org/documentation/self-hosted/Self-Hosted_Engine_Guide/

> In addition, in 4.1 we are introducing a feature which allows HA without
> fencing, in a similar manner to hosted-engine - by a lock on the storage
> side.

For more info on this see:
https://www.ovirt.org/develop/release-management/features/storage/vm-leases/

Nir

> Y.
>
>>
>> There is the option of hosting the engine externally on dedicated
>> hardware, or on another cluster, but then it is still a single point
>> of failure. I recall reading about plans for an HA engine in the
>> future though.
>>
>> Can someone tell me what the roadmap is? Is there a plan to put
>> something like an HA agent on all the hypervisors in the cluster so
>> there is no single point of failure?
>>
>> Thanks for any information,
>>
>> Cam
>> ___
>> 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
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] high availability

[Yaniv Kaul]

On Fri, Feb 3, 2017 at 8:42 PM, cmc  wrote:

> Hi,
>
> I have some questions about oVirt's high availability features for
> VMs. My understanding is that it relies on the engine host to monitor
> and manage the hypervisor hosts, so that in the case of a
> unrecoverable failure of one those hosts, it will fence the host and
> migrate any VM that is designated as highly available to another host
> in the cluster. However, if the engine is itself hosted as a VM on a
> host that fails, this process cannot take place, as the engine will be
> down and cannot initiate monitoring, fencing and migration - is that
> correct?
>

The hosted-engine has its own HA mechanism.
In addition, in 4.1 we are introducing a feature which allows HA without
fencing, in a similar manner to hosted-engine - by a lock on the storage
side.
Y.


> There is the option of hosting the engine externally on dedicated
> hardware, or on another cluster, but then it is still a single point
> of failure. I recall reading about plans for an HA engine in the
> future though.
>
> Can someone tell me what the roadmap is? Is there a plan to put
> something like an HA agent on all the hypervisors in the cluster so
> there is no single point of failure?
>
> Thanks for any information,
>
> Cam
> ___
> 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

[ovirt-users] high availability

[cmc]

Hi,

I have some questions about oVirt's high availability features for
VMs. My understanding is that it relies on the engine host to monitor
and manage the hypervisor hosts, so that in the case of a
unrecoverable failure of one those hosts, it will fence the host and
migrate any VM that is designated as highly available to another host
in the cluster. However, if the engine is itself hosted as a VM on a
host that fails, this process cannot take place, as the engine will be
down and cannot initiate monitoring, fencing and migration - is that
correct?

There is the option of hosting the engine externally on dedicated
hardware, or on another cluster, but then it is still a single point
of failure. I recall reading about plans for an HA engine in the
future though.

Can someone tell me what the roadmap is? Is there a plan to put
something like an HA agent on all the hypervisors in the cluster so
there is no single point of failure?

Thanks for any information,

Cam
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] high availability

[qinglong.d...@horebdata.cn]

Thanks! I'd like to try it out.
 
From: Yaniv Dary
Date: 2017-01-04 19:24
To: qinglong.d...@horebdata.cn
CC: users; Martin Sivak
Subject: Re: [ovirt-users] high availability
In oVirt 4.1 we are planning to allow VM leases that will allow you to restart 
HA VMs in this use case even without power management.
We would love some feedback on this on the latest tested build, if you want to 
try it out:
https://github.com/nirs/ovirt-site/blob/77669161397ebf4cc15c66e0e6876bc033384cfc/source/develop/release-management/features/virt/vm-failover-using-vm-leases.html.md

Yaniv Dary
Technical Product Manager
Red Hat Israel Ltd.
34 Jerusalem Road
Building A, 4th floor
Ra'anana, Israel 4350109
Tel : +972 (9) 7692306
8272306
Email: yd...@redhat.com
IRC : ydary

On Wed, Jan 4, 2017 at 11:33 AM, Martin Sivak <msi...@redhat.com> wrote:
Hi,

high availability requires power management to be configured properly for your 
hosts. The VM won't be restarted until we can ascertain the status of node2 
(because it can still be up).

The host is Non responsive, meaning we do not know if it is up or down. That is 
the reason we show the VM status as unknown.

You can fix that by configuring power management for node2 or by right clicking 
and selecting Confirm host has been rebooted menu option.

Regards

--
Martin Sivak
SLA / oVirt

On Wed, Jan 4, 2017 at 9:45 AM, qinglong.d...@horebdata.cn 
<qinglong.d...@horebdata.cn> wrote:
Hi, all
I have an ovirt 4.0 environment with two hosts and a hosted engine. The 
engine vm was running on host 1 and another vm was running on host2. Then I 
unpluged the power of host 2. The another vm should be supposed to restart on 
host 1 because of ha feature. But it couldn't. It stayed unknown status all the 
time. And the host 2 stayed non responsive status.

Did I understand ha correctly? Anyon can help? 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


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] high availability

[Yaniv Dary]

In oVirt 4.1 we are planning to allow VM leases that will allow you to
restart HA VMs in this use case even without power management.
We would love some feedback on this on the latest tested build, if you want
to try it out:
https://github.com/nirs/ovirt-site/blob/77669161397ebf4cc15c66e0e6876bc033384cfc/source/develop/release-management/features/virt/vm-failover-using-vm-leases.html.md

Yaniv Dary
Technical Product Manager
Red Hat Israel Ltd.
34 Jerusalem Road
Building A, 4th floor
Ra'anana, Israel 4350109

Tel : +972 (9) 7692306
8272306
Email: yd...@redhat.com
IRC : ydary


On Wed, Jan 4, 2017 at 11:33 AM, Martin Sivak  wrote:

> Hi,
>
> high availability requires power management to be configured properly for
> your hosts. The VM won't be restarted until we can ascertain the status of
> node2 (because it can still be up).
>
> The host is Non responsive, meaning we do not know if it is up or down.
> That is the reason we show the VM status as unknown.
>
> You can fix that by configuring power management for node2 or by right
> clicking and selecting Confirm host has been rebooted menu option.
>
> Regards
>
> --
> Martin Sivak
> SLA / oVirt
>
> On Wed, Jan 4, 2017 at 9:45 AM, qinglong.d...@horebdata.cn <
> qinglong.d...@horebdata.cn> wrote:
>
>> Hi, all
>> I have an ovirt 4.0 environment with two hosts and a hosted
>> engine. The engine vm was running on host 1 and another vm was running on
>> host2. Then I unpluged the power of host 2. The another vm should be supposed
>> to restart on host 1 because of ha feature. But it couldn't. It stayed
>> unknown status all the time. And the host 2 stayed non responsive status.
>>
>> Did I understand ha correctly? Anyon can help? 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
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] high availability

[Martin Sivak]

Hi,

high availability requires power management to be configured properly for
your hosts. The VM won't be restarted until we can ascertain the status of
node2 (because it can still be up).

The host is Non responsive, meaning we do not know if it is up or down.
That is the reason we show the VM status as unknown.

You can fix that by configuring power management for node2 or by right
clicking and selecting Confirm host has been rebooted menu option.

Regards

--
Martin Sivak
SLA / oVirt

On Wed, Jan 4, 2017 at 9:45 AM, qinglong.d...@horebdata.cn <
qinglong.d...@horebdata.cn> wrote:

> Hi, all
> I have an ovirt 4.0 environment with two hosts and a hosted
> engine. The engine vm was running on host 1 and another vm was running on
> host2. Then I unpluged the power of host 2. The another vm should be supposed
> to restart on host 1 because of ha feature. But it couldn't. It stayed
> unknown status all the time. And the host 2 stayed non responsive status.
>
> Did I understand ha correctly? Anyon can help? 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

[ovirt-users] high availability

[qinglong.d...@horebdata.cn]

Hi, all
I have an ovirt 4.0 environment with two hosts and a hosted engine. The 
engine vm was running on host 1 and another vm was running on host2. Then I 
unpluged the power of host 2. The another vm should be supposed to restart on 
host 1 because of ha feature. But it couldn't. It stayed unknown status all the 
time. And the host 2 stayed non responsive status.

Did I understand ha correctly? Anyon can help? Thanks!
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] High Availability OVirt

[victor nunes]

OK.

Thanks


2013/4/20 Itamar Heim ih...@redhat.com

 On 04/19/2013 02:41 PM, René Koch (ovido) wrote:

 Hi,

 You can use a cluster software like pacemaker or RH Cluster to make your
 ovirt-engine high available.

 I personally recommend to virtualise it on a KVM host, as keeping
 virtual machines high available is much easier then making all services
 ovirt-engine need high available (but it's possible for sure).

 So what happens when your engine hosts goes down:
 - You can't login into webadmin and user portals
 - high availability and live migration features of your virtual machines
 aren't working
 - You can't start/deploy new virtual machines
 - Your hosts and virtual machines that are already running stay up of
 course

 As clustering brings in more complexity I would use a server with RAID,
 redundant power supplies and redundant network interfaces (bonding) for
 ovirt-engine instead of clustering. Only when using desktop
 virtualization where availabilty of the user portal is really important
 I would cluster ovirt-engine.
 (But this is just my personal opinion)


 and we're looking at a hosted engine which will try to solve this out of
 the box.




 Regards,
 René



 On Fri, 2013-04-19 at 08:19 -0300, victor nunes wrote:


 Is there any way to create redundancy oVirt-engine?
 We install oVirt-engine in a machine, and what happens if that burning
 machine?


 Is there anything that can be done to remedy this?


 Att,
 --
 “Encarada do ponto de vista da juventude, a vida parece um futuro
 indefinidamente longo, ao passo que, na velhice, ela parece um
 passado
 deveras curto. Assim, a vida no seu início se apresenta do mesmo modo
 que as coisas quando as olhamos através de um binóculo usado ao
 contrário; mas, ao
 seu final, ela se parece com as coisas  tal qual são vistas quando o
 binóculo
 é usado de modo normal. Um homem precisa ter envelhecido e vivido
 bastante para perceber como a vida é curta”.

   (Poema de Arthur Schopenhauer)
 __**_
 Users mailing list
 Users@ovirt.org
 http://lists.ovirt.org/**mailman/listinfo/usershttp://lists.ovirt.org/mailman/listinfo/users


 __**_
 Users mailing list
 Users@ovirt.org
 http://lists.ovirt.org/**mailman/listinfo/usershttp://lists.ovirt.org/mailman/listinfo/users





-- 
“Encarada do ponto de vista da juventude, a vida parece um futuro
indefinidamente longo, ao passo que, na velhice, ela parece um passado
deveras curto. Assim, a vida no seu início se apresenta do mesmo modo
que as coisas quando as olhamos através de um binóculo usado ao contrário;
mas, ao
seu final, ela se parece com as coisas  tal qual são vistas quando o
binóculo
é usado de modo normal. Um homem precisa ter envelhecido e vivido
bastante para perceber como a vida é curta”.

 (Poema de Arthur Schopenhauer)
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[Users] High Availability OVirt

[victor nunes]

Is there any way to create redundancy oVirt-engine?
We install oVirt-engine in a machine, and what happens if that burning
machine?

Is there anything that can be done to remedy this?

Att,
-- 
“Encarada do ponto de vista da juventude, a vida parece um futuro
indefinidamente longo, ao passo que, na velhice, ela parece um passado
deveras curto. Assim, a vida no seu início se apresenta do mesmo modo
que as coisas quando as olhamos através de um binóculo usado ao contrário;
mas, ao
seu final, ela se parece com as coisas  tal qual são vistas quando o
binóculo
é usado de modo normal. Um homem precisa ter envelhecido e vivido
bastante para perceber como a vida é curta”.

 (Poema de Arthur Schopenhauer)
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] High Availability OVirt

[Koch (ovido)]

Hi,

You can use a cluster software like pacemaker or RH Cluster to make your
ovirt-engine high available.

I personally recommend to virtualise it on a KVM host, as keeping
virtual machines high available is much easier then making all services
ovirt-engine need high available (but it's possible for sure).

So what happens when your engine hosts goes down:
- You can't login into webadmin and user portals
- high availability and live migration features of your virtual machines
aren't working
- You can't start/deploy new virtual machines
- Your hosts and virtual machines that are already running stay up of
course

As clustering brings in more complexity I would use a server with RAID,
redundant power supplies and redundant network interfaces (bonding) for
ovirt-engine instead of clustering. Only when using desktop
virtualization where availabilty of the user portal is really important
I would cluster ovirt-engine.
(But this is just my personal opinion)



Regards,
René



On Fri, 2013-04-19 at 08:19 -0300, victor nunes wrote:
 
 Is there any way to create redundancy oVirt-engine?
 We install oVirt-engine in a machine, and what happens if that burning
 machine?
 
 
 Is there anything that can be done to remedy this?
 
 
 Att,
 -- 
 “Encarada do ponto de vista da juventude, a vida parece um futuro
 indefinidamente longo, ao passo que, na velhice, ela parece um
 passado 
 deveras curto. Assim, a vida no seu início se apresenta do mesmo modo
 que as coisas quando as olhamos através de um binóculo usado ao
 contrário; mas, ao 
 seu final, ela se parece com as coisas  tal qual são vistas quando o
 binóculo
 é usado de modo normal. Um homem precisa ter envelhecido e vivido
 bastante para perceber como a vida é curta”.
 
  (Poema de Arthur Schopenhauer)
 ___
 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

Re: [Users] High Availability

[suporte]

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.k...@ovido.at
Para: supo...@logicworks.pt
Cc: Shu Ming shum...@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 +, supo...@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 shum...@linux.vnet.ibm.com
 Para: Tim Hildred thild...@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: thild...@redhat.com
  Internal: 8588287
  Mobile: +61 4 666 25242
  IRC: thildred
 
  - Original Message -
  From: Shu Ming shum...@linux.vnet.ibm.com
  To: Tim Hildred thild...@redhat.com
  Cc: d...@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_Virtualization/3.1/html/Administration_Guide/High_availability_considerations.html
  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

Re: [Users] High Availability

[Gianluca Cecchi]

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
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] High Availability

[suporte]

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.cec...@gmail.com
Para: supo...@logicworks.pt
Cc: René Koch (ovido) r.k...@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
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] High Availability

[Gianluca Cecchi]

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
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] High Availability

[suporte]

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 supply to 
previse this scenario? 

- Original Message -

From: René Koch r.k...@ovido.at 
To: supo...@logicworks.pt, Gianluca Cecchi gianluca.cec...@gmail.com 
Cc: users Users@ovirt.org 
Sent: Terça-feira, 16 de Abril de 2013 13:31:48 
Subject: RE: [Users] High Availability 



-Original message- 
 From:supo...@logicworks.pt supo...@logicworks.pt 
 Sent: Tuesday 16th April 2013 14:03 
 To: Gianluca Cecchi gianluca.cec...@gmail.com 
 Cc: René Koch r.k...@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.cec...@gmail.com 
 Para: supo...@logicworks.pt 
 Cc: René Koch (ovido) r.k...@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 
 

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] High Availability

[suporte]

Ok, now I understand, so what do we need to get the power management configured 
and working? 

Regards 
Jose 

- Mensagem original -

De: Shu Ming shum...@linux.vnet.ibm.com 
Para: Tim Hildred thild...@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: thild...@redhat.com 
 Internal: 8588287 
 Mobile: +61 4 666 25242 
 IRC: thildred 
 
 - Original Message - 
 From: Shu Ming shum...@linux.vnet.ibm.com 
 To: Tim Hildred thild...@redhat.com 
 Cc: d...@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_Virtualization/3.1/html/Administration_Guide/High_availability_considerations.html
  
 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: thild...@redhat.com Internal: 8588287 
 Mobile: +61 4 666 25242 
 IRC: thildred 
 
 - Original Message - 
 
 From: Dafna Ron d...@redhat.com To: supo...@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, supo...@logicworks.pt wrote: 
 
 Is it Mandatory to have power manamement enabled? if yes what 
 equipment do you recommend to use with it? 
 
 Regards 
 Jose

Re: [Users] High Availability

[Koch (ovido)]

On Mon, 2013-03-18 at 09:50 +, supo...@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 shum...@linux.vnet.ibm.com
 Para: Tim Hildred thild...@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: thild...@redhat.com
  Internal: 8588287
  Mobile: +61 4 666 25242
  IRC: thildred
 
  - Original Message -
  From: Shu Ming shum...@linux.vnet.ibm.com
  To: Tim Hildred thild...@redhat.com
  Cc: d...@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_Virtualization/3.1/html/Administration_Guide/High_availability_considerations.html
  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: thild...@redhat.com Internal: 8588287
  Mobile: +61 4 666 25242
  IRC: thildred
 
  - Original Message -
 
  From: Dafna Ron d...@redhat.com To: supo...@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

[Users] High Availability

[suporte]

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

Re: [Users] High Availability

[Noam Slomianko]

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: supo...@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
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] High Availability

[René Koch]

Hi,

You have to configure power management to make high availability working and 
mark the vms high availability checkbox...


Regards,
René
 
 
-Original message-
 From:supo...@logicworks.pt supo...@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

Re: [Users] High Availability

[suporte]

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.k...@ovido.at
Para: supo...@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:supo...@logicworks.pt supo...@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

Re: [Users] High Availability

[Dafna Ron]

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, supo...@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.k...@ovido.at
 Para: supo...@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:supo...@logicworks.pt supo...@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

Re: [Users] High Availability

[Tim Hildred]

You might also find this helpful:
https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Virtualization/3.1/html/Administration_Guide/High_availability_considerations.html

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: thild...@redhat.com
Internal: 8588287
Mobile: +61 4 666 25242
IRC: thildred

- Original Message -
 From: Dafna Ron d...@redhat.com
 To: supo...@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, supo...@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.k...@ovido.at
  Para: supo...@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:supo...@logicworks.pt supo...@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

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. 

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: thild...@redhat.com
Internal: 8588287
Mobile: +61 4 666 25242
IRC: thildred

- Original Message -
 From: Shu Ming shum...@linux.vnet.ibm.com
 To: Tim Hildred thild...@redhat.com
 Cc: d...@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_Virtualization/3.1/html/Administration_Guide/High_availability_considerations.html
 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: thild...@redhat.com Internal: 8588287
 Mobile: +61 4 666 25242
 IRC: thildred
 
 - Original Message -
 
 From: Dafna Ron d...@redhat.com To: supo...@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, supo...@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.k...@ovido.at Para: supo...@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:supo...@logicworks.pt supo...@logicworks.pt Sent: Sunday 17th
 March 2013 17:28
 To: Users@ovirt.org Subject

Re: [Users] High Availability

[Shu Ming]

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: thild...@redhat.com
Internal: 8588287
Mobile: +61 4 666 25242
IRC: thildred

- Original Message -

From: Shu Ming shum...@linux.vnet.ibm.com
To: Tim Hildred thild...@redhat.com
Cc: d...@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_Virtualization/3.1/html/Administration_Guide/High_availability_considerations.html
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: thild...@redhat.com Internal: 8588287
Mobile: +61 4 666 25242
IRC: thildred

- Original Message -

From: Dafna Ron d...@redhat.com To: supo...@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, supo...@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.k...@ovido.at Para: supo...@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:supo...@logicworks.pt supo...@logicworks.pt Sent: Sunday 17th
March 2013 17:28
To: Users@ovirt.org Subject: [Users] High Availability

What should I

Re: [Users] high availability via fencing

[Eli Mesika]

- Original Message -
 From: Dan Kenigsberg dan...@redhat.com
 To: Ian Levesque i...@crystal.harvard.edu
 Cc: Eli Mesika emes...@redhat.com, users@ovirt.org
 Sent: Wednesday, April 25, 2012 7:59:08 AM
 Subject: Re: [Users] high availability via fencing
 
 On Tue, Apr 24, 2012 at 12:20:37PM -0400, Ian Levesque wrote:
   2012-04-20 11:32:44,696 INFO
   [org.ovirt.engine.core.vdsbroker.vdsbroker.FenceVdsVDSCommand]
   (http--0.0.0.0-8443-5) FINISH, FenceVdsVDSCommand, return: Test
   Failed, Host Status is: unknown. The fence-agent script reported
   the
   following error: Failed: You have to enter plug number
   Please use '-h' for usage
   
   I've tried to add port=1 to the Options field but that seems
   to
   have no effect.
   
   Any ideas? Is there any way to configure a dumb power
   management /
   fencing configuration for testing?
   
   If you still have the problem, can you please put also the vdsm
   log (look for fenceNode )
   Thanks
  
  Hi Eli,
  
  Here is the relevant output, though I don't think it'll be much
  more help:
 
 Actually, it does, since it shows that Vdsm did not receive any
 'port'
 to pass to fence_apc, which is required. 'port' is usually the
 ordinal
 postion of your blade. Either define it in the GUI or use port=n
 option in the options edit box.

This is the line from the engine log

2012-04-20 11:32:44,598 INFO  
[org.ovirt.engine.core.vdsbroker.vdsbroker.FenceVdsVDSCommand] 
(http--0.0.0.0-8443-5) START, FenceVdsVDSCommand(vdsId = 
6de5e3fa-8a33-11e1-b3f9-003048c85226, targetVdsId = 
60087c5e-8a3b-11e1-b15d-003048c85226, action = Status, ip = 134.174.x.x, port = 
, type = apc, user = ovirt, password = **, options = 
'port=22,secure=true,slot=1'), log id: 57f86a56

So, what I see is that port was sent twice , once as empty and then the port=22 
is sent as part of the options string.

Can you please remove the port from the options field and put it in the port 
field.
If this works , this is an engine core bug...

 
  
  Thread-1818::DEBUG::2012-04-24
  12:17:59,804::API::954::vds::(fenceNode)
  fenceNode(addr=134.174.x.x,port=,agent=apc,user=ovirt,passwd=,action=status,secure=,options=)
  Thread-1818::DEBUG::2012-04-24
  12:17:59,841::API::980::vds::(fenceNode) rc 1 in agent=fence_apc
  ipaddr=134.174.x.x
  login=ovirt
  option=status
  passwd=
   out  err Failed: You have to enter plug number
  Please use '-h' for usage
  
  Thanks,
  Ian
  ___
  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

Re: [Users] high availability via fencing

[Dan Kenigsberg]

On Wed, Apr 25, 2012 at 05:13:40AM -0400, Eli Mesika wrote:
 
 
 - Original Message -
  From: Dan Kenigsberg dan...@redhat.com
  To: Ian Levesque i...@crystal.harvard.edu
  Cc: Eli Mesika emes...@redhat.com, users@ovirt.org
  Sent: Wednesday, April 25, 2012 7:59:08 AM
  Subject: Re: [Users] high availability via fencing
  
  On Tue, Apr 24, 2012 at 12:20:37PM -0400, Ian Levesque wrote:
2012-04-20 11:32:44,696 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.FenceVdsVDSCommand]
(http--0.0.0.0-8443-5) FINISH, FenceVdsVDSCommand, return: Test
Failed, Host Status is: unknown. The fence-agent script reported
the
following error: Failed: You have to enter plug number
Please use '-h' for usage

I've tried to add port=1 to the Options field but that seems
to
have no effect.

Any ideas? Is there any way to configure a dumb power
management /
fencing configuration for testing?

If you still have the problem, can you please put also the vdsm
log (look for fenceNode )
Thanks
   
   Hi Eli,
   
   Here is the relevant output, though I don't think it'll be much
   more help:
  
  Actually, it does, since it shows that Vdsm did not receive any
  'port'
  to pass to fence_apc, which is required. 'port' is usually the
  ordinal
  postion of your blade. Either define it in the GUI or use port=n
  option in the options edit box.
 
 This is the line from the engine log
 
 2012-04-20 11:32:44,598 INFO  
 [org.ovirt.engine.core.vdsbroker.vdsbroker.FenceVdsVDSCommand] 
 (http--0.0.0.0-8443-5) START, FenceVdsVDSCommand(vdsId = 
 6de5e3fa-8a33-11e1-b3f9-003048c85226, targetVdsId = 
 60087c5e-8a3b-11e1-b15d-003048c85226, action = Status, ip = 134.174.x.x, port 
 = , type = apc, user = ovirt, password = **, options = 
 'port=22,secure=true,slot=1'), log id: 57f86a56
 
 So, what I see is that port was sent twice , once as empty and then the 
 port=22 is sent as part of the options string.
 
 Can you please remove the port from the options field and put it in the port 
 field.
 If this works , this is an engine core bug...

I believe that it is such a bug, since the options field come up as
empty in vdsm.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] high availability via fencing

[Ian Levesque]

 So, what I see is that port was sent twice , once as empty and then the 
 port=22 is sent as part of the options string.
 
 Can you please remove the port from the options field and put it in the port 
 field.
 If this works , this is an engine core bug...
 
 I believe that it is such a bug, since the options field come up as
 empty in vdsm.

I tried entering a Port, Slot and plug=1 in options. I also checked Secure. 
It indeed appears that the engine isn't passing the options along. I also find 
it odd that a required field (plug) isn't available via a form field. Is that 
just a side effect? I can file a bug -- does it belong in ovirt-engine-core?

Here's the vdsm and engine log output when I click Test:


== ../ovirt-engine/engine.log ==
2012-04-25 12:18:50,302 INFO  [org.ovirt.engine.core.bll.FencingExecutor] 
(http--0.0.0.0-8443-4) Executing Status Power Management command, Proxy 
Host:heilig, Agent:apc, Target Host:, Management IP:134.174.x.x, User:ovirt, 
Options:port=22,plug=1,secure=true,slot=1

2012-04-25 12:18:50,305 INFO  
[org.ovirt.engine.core.vdsbroker.vdsbroker.FenceVdsVDSCommand] 
(http--0.0.0.0-8443-4) START, FenceVdsVDSCommand(vdsId = 
6de5e3fa-8a33-11e1-b3f9-003048c85226, targetVdsId = 
60087c5e-8a3b-11e1-b15d-003048c85226, action = Status, ip = 134.174.x.x, port = 
, type = apc, user = ovirt, password = **, options = 
'port=22,plug=1,secure=true,slot=1'), log id: 56a240f9


== vdsm.log ==
Thread-52872::DEBUG::2012-04-25 12:18:50,311::API::954::vds::(fenceNode) 
fenceNode(addr=134.174.x.x,port=,agent=apc,user=ovirt,passwd=,action=status,secure=,options=)
Thread-52872::DEBUG::2012-04-25 12:18:50,348::API::980::vds::(fenceNode) rc 1 
in agent=fence_apc
ipaddr=134.174.x.x
login=ovirt
option=status
passwd=
 out  err Failed: You have to enter plug number
Please use '-h' for usage

Thread-52873::DEBUG::2012-04-25 12:18:50,356::API::954::vds::(fenceNode) 
fenceNode(addr=134.174.x.x,port=,agent=apc,user=ovirt,passwd=,action=status,secure=,options=)
Thread-52873::DEBUG::2012-04-25 12:18:50,392::API::980::vds::(fenceNode) rc 1 
in agent=fence_apc
ipaddr=134.174.x.x
login=ovirt
option=status
passwd=
 out  err Failed: You have to enter plug number
Please use '-h' for usage


Thanks,
Ian
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] high availability via fencing

[Ian Levesque]

 2012-04-20 11:32:44,696 INFO
 [org.ovirt.engine.core.vdsbroker.vdsbroker.FenceVdsVDSCommand]
 (http--0.0.0.0-8443-5) FINISH, FenceVdsVDSCommand, return: Test
 Failed, Host Status is: unknown. The fence-agent script reported the
 following error: Failed: You have to enter plug number
 Please use '-h' for usage
 
 I've tried to add port=1 to the Options field but that seems to
 have no effect.
 
 Any ideas? Is there any way to configure a dumb power management /
 fencing configuration for testing?
 
 If you still have the problem, can you please put also the vdsm log (look for 
 fenceNode )
 Thanks

Hi Eli,

Here is the relevant output, though I don't think it'll be much more help:

Thread-1818::DEBUG::2012-04-24 12:17:59,804::API::954::vds::(fenceNode) 
fenceNode(addr=134.174.x.x,port=,agent=apc,user=ovirt,passwd=,action=status,secure=,options=)
Thread-1818::DEBUG::2012-04-24 12:17:59,841::API::980::vds::(fenceNode) rc 1 in 
agent=fence_apc
ipaddr=134.174.x.x
login=ovirt
option=status
passwd=
 out  err Failed: You have to enter plug number
Please use '-h' for usage

Thanks,
Ian
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [Users] high availability via fencing

[Dan Kenigsberg]

On Tue, Apr 24, 2012 at 12:20:37PM -0400, Ian Levesque wrote:
  2012-04-20 11:32:44,696 INFO
  [org.ovirt.engine.core.vdsbroker.vdsbroker.FenceVdsVDSCommand]
  (http--0.0.0.0-8443-5) FINISH, FenceVdsVDSCommand, return: Test
  Failed, Host Status is: unknown. The fence-agent script reported the
  following error: Failed: You have to enter plug number
  Please use '-h' for usage
  
  I've tried to add port=1 to the Options field but that seems to
  have no effect.
  
  Any ideas? Is there any way to configure a dumb power management /
  fencing configuration for testing?
  
  If you still have the problem, can you please put also the vdsm log (look 
  for fenceNode )
  Thanks
 
 Hi Eli,
 
 Here is the relevant output, though I don't think it'll be much more help:

Actually, it does, since it shows that Vdsm did not receive any 'port'
to pass to fence_apc, which is required. 'port' is usually the ordinal
postion of your blade. Either define it in the GUI or use port=n
option in the options edit box.

 
 Thread-1818::DEBUG::2012-04-24 12:17:59,804::API::954::vds::(fenceNode) 
 fenceNode(addr=134.174.x.x,port=,agent=apc,user=ovirt,passwd=,action=status,secure=,options=)
 Thread-1818::DEBUG::2012-04-24 12:17:59,841::API::980::vds::(fenceNode) rc 1 
 in agent=fence_apc
 ipaddr=134.174.x.x
 login=ovirt
 option=status
 passwd=
  out  err Failed: You have to enter plug number
 Please use '-h' for usage
 
 Thanks,
 Ian
 ___
 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

Re: [Users] high availability via fencing

[Eli Mesika]

- Original Message -
 From: Ian Levesque i...@crystal.harvard.edu
 To: users@ovirt.org
 Sent: Friday, April 20, 2012 6:36:16 PM
 Subject: [Users] high availability via fencing
 
 Hello,
 
 I'm testing ovirt for potential deployment and one of the metrics for
 its success relies on the high availability feature. In my research
 on this feature, I found scattered documentation indicating that
 fencing is a prerequisite. On my test hardware, I don't have any
 LOM/IPMI but I see that APC managed PDUs are supported, which I do
 have.
 
 The problem is when I try to configure Power Management to use the
 apc type, I get this error:
 
   Test Failed, Host Status is: unknown. The fence-agent script
   reported the following error:
   Failed: You have to enter plug number Please use '-h' for usage
 
 ovirt-engine/engine.log tells me:
 
 2012-04-20 11:32:44,595 INFO
  [org.ovirt.engine.core.bll.FencingExecutor] (http--0.0.0.0-8443-5)
 Executing Status Power Management command, Proxy Host:heilig,
 Agent:apc, Target Host:, Management IP:134.174.x.x, User:ovirt,
 Options:port=22,secure=true,slot=1
 
 2012-04-20 11:32:44,598 INFO
  [org.ovirt.engine.core.vdsbroker.vdsbroker.FenceVdsVDSCommand]
 (http--0.0.0.0-8443-5) START, FenceVdsVDSCommand(vdsId =
 6de5e3fa-8a33-11e1-b3f9-003048c85226, targetVdsId =
 60087c5e-8a3b-11e1-b15d-003048c85226, action = Status, ip =
 134.174.x.x, port = , type = apc, user = ovirt, password = **,
 options = 'port=22,secure=true,slot=1'), log id: 57f86a56
 
 2012-04-20 11:32:44,696 INFO
  [org.ovirt.engine.core.vdsbroker.vdsbroker.FenceVdsVDSCommand]
 (http--0.0.0.0-8443-5) FINISH, FenceVdsVDSCommand, return: Test
 Failed, Host Status is: unknown. The fence-agent script reported the
 following error: Failed: You have to enter plug number
 Please use '-h' for usage
 
 I've tried to add port=1 to the Options field but that seems to
 have no effect.
 
 Any ideas? Is there any way to configure a dumb power management /
 fencing configuration for testing?

If you still have the problem, can you please put also the vdsm log (look for 
fenceNode )
Thanks

 
 Cheers,
 Ian
 ___
 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

[Users] high availability via fencing

[Ian Levesque]

Hello,

I'm testing ovirt for potential deployment and one of the metrics for its 
success relies on the high availability feature. In my research on this 
feature, I found scattered documentation indicating that fencing is a 
prerequisite. On my test hardware, I don't have any LOM/IPMI but I see that APC 
managed PDUs are supported, which I do have.

The problem is when I try to configure Power Management to use the apc type, 
I get this error:

Test Failed, Host Status is: unknown. The fence-agent script reported 
the following error: 
Failed: You have to enter plug number Please use '-h' for usage

ovirt-engine/engine.log tells me:

2012-04-20 11:32:44,595 INFO  [org.ovirt.engine.core.bll.FencingExecutor] 
(http--0.0.0.0-8443-5) Executing Status Power Management command, Proxy 
Host:heilig, Agent:apc, Target Host:, Management IP:134.174.x.x, User:ovirt, 
Options:port=22,secure=true,slot=1

2012-04-20 11:32:44,598 INFO  
[org.ovirt.engine.core.vdsbroker.vdsbroker.FenceVdsVDSCommand] 
(http--0.0.0.0-8443-5) START, FenceVdsVDSCommand(vdsId = 
6de5e3fa-8a33-11e1-b3f9-003048c85226, targetVdsId = 
60087c5e-8a3b-11e1-b15d-003048c85226, action = Status, ip = 134.174.x.x, port = 
, type = apc, user = ovirt, password = **, options = 
'port=22,secure=true,slot=1'), log id: 57f86a56

2012-04-20 11:32:44,696 INFO  
[org.ovirt.engine.core.vdsbroker.vdsbroker.FenceVdsVDSCommand] 
(http--0.0.0.0-8443-5) FINISH, FenceVdsVDSCommand, return: Test Failed, Host 
Status is: unknown. The fence-agent script reported the following error: 
Failed: You have to enter plug number
Please use '-h' for usage

I've tried to add port=1 to the Options field but that seems to have no 
effect.

Any ideas? Is there any way to configure a dumb power management / fencing 
configuration for testing?

Cheers,
Ian
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users