9:23 p.m.
--=_6b64648d-a388-4684-810e-c55884b4d006
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Howdy all,
we're testing ovirt at the moment, and trying to get power management working for the
dell PE1950's we're using as the hypervisors...
in RHEV3 beta, we used to use the console IP, U&P and type "ilo3" to monitor
power states etc..
in the ovirt manager, trying to set the same config up - it says
Test Failed (unknown error).
and in the engine.log it shows
2012-02-02 02:34:09,385 ERROR [org.ovirt.engine.core.bll.FencingExecutor]
(http--0.0.0.0-8080-2) Failed to run Power Management command on Host , no running proxy
Host was found.
Any ideas?
Cheers
Spyro
--=_6b64648d-a388-4684-810e-c55884b4d006
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit
<html><head><style type='text/css'>p { margin: 0;
}</style></head><body><div style='font-family: tahoma,new
york,times,serif; font-size: 12pt; color: #000000'>Howdy all,
<br><br>we're testing ovirt at the moment, and trying to get
power management working for the dell PE1950's we're using as the
hypervisors...<br>in RHEV3 beta, we used to use the console IP, U&P and type
"ilo3" to monitor power states etc..<br><br>in the ovirt manager,
trying to set the same config up - it says <br><div class="GFBBYDSCMYB"
style="overflow: auto; position: relative;"><div style="position:
relative;"><div class="gwt-Label">Test Failed (unknown
error).<br><br>and in the engine.log it
shows<br></div></div></div><span class="Object"
id="OBJ_PREFIX_DWT8483_com_zimbra_date">2012-02-02</span>
02:34:09,385 ERROR [org.ovirt.engine.core.bll.FencingExecutor]
(http--0.0.0.0-8080-2) Failed to run Power Management command on Host ,
no running proxy Host was found.<br><br>Any
ideas?<br><br>Cheers<br>Spyro<br></div></body></html>
--=_6b64648d-a388-4684-810e-c55884b4d006--
5:04 a.m.
On 02/01/2012 09:53 PM, Spyro Polymiadis wrote:
Howdy all,
we're testing ovirt at the moment, and trying to get power management
working for the dell PE1950's we're using as the hypervisors...
in RHEV3 beta, we used to use the console IP, U&P and type "ilo3" to
monitor power states etc..
in the ovirt manager, trying to set the same config up - it says
Test Failed (unknown error).
and in the engine.log it shows
2012-02-02 02:34:09,385 ERROR
[org.ovirt.engine.core.bll.FencingExecutor] (http--0.0.0.0-8080-2)
Failed to run Power Management command on Host , no running proxy Host
was found.
Just a stab in the dark here... how many hypervisor nodes are running in
the same cluster?
The way fencing works (iirc) is if you want to fence HostA, you need to
have a separate HostB running so that HostB can issue the fence command
to HostA. So if there's just a single node running, there's no one else
to proxy the fencing command to that host. I don't think the oVirt
Engine server ever directly fences hosts, it just tells a remote vdsm to
do it on its behalf.
9:43 p.m.
so, if i read that right - does this mean that i need to have 2 nodes in the cluster to
get this working (thats the only difference from the rhev environment) i havent moved the
other hypervisors into it yet...
i figured the manager host could perform the power management..
----- Original Message -----
From: "Perry Myers" <pmyers(a)redhat.com>
To: "Spyro Polymiadis" <spyro(a)rsp.com.au>
Cc: users(a)ovirt.org
Sent: Thursday, 2 February, 2012 1:34:18 PM
Subject: Re: [Users] Power Management question
On 02/01/2012 09:53 PM, Spyro Polymiadis wrote:
Howdy all,
we're testing ovirt at the moment, and trying to get power management
working for the dell PE1950's we're using as the hypervisors...
in RHEV3 beta, we used to use the console IP, U&P and type "ilo3" to
monitor power states etc..
in the ovirt manager, trying to set the same config up - it says
Test Failed (unknown error).
and in the engine.log it shows
2012-02-02 02:34:09,385 ERROR
[org.ovirt.engine.core.bll.FencingExecutor] (http--0.0.0.0-8080-2)
Failed to run Power Management command on Host , no running proxy Host
was found.
Just a stab in the dark here... how many hypervisor nodes are running in
the same cluster?
The way fencing works (iirc) is if you want to fence HostA, you need to
have a separate HostB running so that HostB can issue the fence command
to HostA. So if there's just a single node running, there's no one else
to proxy the fencing command to that host. I don't think the oVirt
Engine server ever directly fences hosts, it just tells a remote vdsm to
do it on its behalf.
5:16 a.m.
On 02/01/2012 10:13 PM, Spyro Polymiadis wrote:
so, if i read that right - does this mean that i need to have 2
nodes
in the cluster to get this working (thats the only difference from
the rhev environment) i havent moved the other hypervisors into it
yet... i figured the manager host could perform the power
management..
That's my understanding, but I could be wrong :) The vdsm/oVirt Engine
folks would know better
Try moving a 2nd host over and see if that resolves the issue
10:57 a.m.
Hi,
Yes, the ovirt backend does not shut down or power up any hosts directly, it can work only
through vdsm. Therefore you need one running host per datacenter to be able to manage the
rest of the hosts.
I understand the motivation, but for smaller installations I believe it would be so great
if the backend could do it as well. What vdsm does in the background is not much more than
calling the ipmipower command.
Laszlo
----- Original Message -----
From: "Perry Myers" <pmyers(a)redhat.com>
To: "Spyro Polymiadis" <spyro(a)rsp.com.au>
Cc: users(a)ovirt.org
Sent: Thursday, February 2, 2012 4:16:12 AM
Subject: Re: [Users] Power Management question
On 02/01/2012 10:13 PM, Spyro Polymiadis wrote:
> so, if i read that right - does this mean that i need to have 2
> nodes
> in the cluster to get this working (thats the only difference from
> the rhev environment) i havent moved the other hypervisors into it
> yet... i figured the manager host could perform the power
> management..
That's my understanding, but I could be wrong :) The vdsm/oVirt
Engine
folks would know better
Try moving a 2nd host over and see if that resolves the issue
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
1:05 p.m.
On 02/02/12 10:57, Laszlo Hornyak wrote:
Hi,
Yes, the ovirt backend does not shut down or power up any hosts directly, it can work
only through vdsm. Therefore you need one running host per datacenter to be able to manage
the rest of the hosts.
I understand the motivation, but for smaller installations I believe it would be so great
if the backend could do it as well. What vdsm does in the background is not much more than
calling the ipmipower command.
I agree, there is no real reason not to fence hosts from the management
host, yet another feature we would love to have.
Worth checking if the engine can reuse the vdsm code for fencing.
Laszlo
----- Original Message -----
> From: "Perry Myers" <pmyers(a)redhat.com>
> To: "Spyro Polymiadis" <spyro(a)rsp.com.au>
> Cc: users(a)ovirt.org
> Sent: Thursday, February 2, 2012 4:16:12 AM
> Subject: Re: [Users] Power Management question
>
> On 02/01/2012 10:13 PM, Spyro Polymiadis wrote:
>> so, if i read that right - does this mean that i need to have 2
>> nodes
>> in the cluster to get this working (thats the only difference from
>> the rhev environment) i havent moved the other hypervisors into it
>> yet... i figured the manager host could perform the power
>> management..
>
> That's my understanding, but I could be wrong :) The vdsm/oVirt
> Engine
> folks would know better
>
> Try moving a 2nd host over and see if that resolves the issue
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
1:41 p.m.
----- Original Message -----
On 02/02/12 10:57, Laszlo Hornyak wrote:
> Hi,
>
> Yes, the ovirt backend does not shut down or power up any hosts
> directly, it can work only through vdsm. Therefore you need one
> running host per datacenter to be able to manage the rest of the
> hosts.
>
> I understand the motivation, but for smaller installations I
> believe it would be so great if the backend could do it as well.
> What vdsm does in the background is not much more than calling the
> ipmipower command.
>
I agree, there is no real reason not to fence hosts from the
management
host, yet another feature we would love to have.
Worth checking if the engine can reuse the vdsm code for fencing.
This would come for free once we have the all in one (vdsm running on the same host as
engine).
> Laszlo
>
> ----- Original Message -----
>> From: "Perry Myers" <pmyers(a)redhat.com>
>> To: "Spyro Polymiadis" <spyro(a)rsp.com.au>
>> Cc: users(a)ovirt.org
>> Sent: Thursday, February 2, 2012 4:16:12 AM
>> Subject: Re: [Users] Power Management question
>>
>> On 02/01/2012 10:13 PM, Spyro Polymiadis wrote:
>>> so, if i read that right - does this mean that i need to have 2
>>> nodes
>>> in the cluster to get this working (thats the only difference
>>> from
>>> the rhev environment) i havent moved the other hypervisors into
>>> it
>>> yet... i figured the manager host could perform the power
>>> management..
>>
>> That's my understanding, but I could be wrong :) The vdsm/oVirt
>> Engine
>> folks would know better
>>
>> Try moving a 2nd host over and see if that resolves the issue
>> _______________________________________________
>> Users mailing list
>> Users(a)ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
1:46 p.m.
On 02/02/12 13:41, Ayal Baron wrote:
----- Original Message -----
> On 02/02/12 10:57, Laszlo Hornyak wrote:
>> Hi,
>>
>> Yes, the ovirt backend does not shut down or power up any hosts
>> directly, it can work only through vdsm. Therefore you need one
>> running host per datacenter to be able to manage the rest of the
>> hosts.
>>
>> I understand the motivation, but for smaller installations I
>> believe it would be so great if the backend could do it as well.
>> What vdsm does in the background is not much more than calling the
>> ipmipower command.
>>
>
> I agree, there is no real reason not to fence hosts from the
> management
> host, yet another feature we would love to have.
>
> Worth checking if the engine can reuse the vdsm code for fencing.
This would come for free once we have the all in one (vdsm running on the same host as
engine).
We'll get it for 'free' when installing VDSM on the same host as the
engine, but the above can be useful even if the user don't install VDSM
on the engine machine.
>
>
>> Laszlo
>>
>> ----- Original Message -----
>>> From: "Perry Myers" <pmyers(a)redhat.com>
>>> To: "Spyro Polymiadis" <spyro(a)rsp.com.au>
>>> Cc: users(a)ovirt.org
>>> Sent: Thursday, February 2, 2012 4:16:12 AM
>>> Subject: Re: [Users] Power Management question
>>>
>>> On 02/01/2012 10:13 PM, Spyro Polymiadis wrote:
>>>> so, if i read that right - does this mean that i need to have 2
>>>> nodes
>>>> in the cluster to get this working (thats the only difference
>>>> from
>>>> the rhev environment) i havent moved the other hypervisors into
>>>> it
>>>> yet... i figured the manager host could perform the power
>>>> management..
>>>
>>> That's my understanding, but I could be wrong :) The vdsm/oVirt
>>> Engine
>>> folks would know better
>>>
>>> Try moving a 2nd host over and see if that resolves the issue
>>> _______________________________________________
>>> Users mailing list
>>> Users(a)ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/users
>>>
>> _______________________________________________
>> Users mailing list
>> Users(a)ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
1:54 p.m.
----- Original Message -----
On 02/02/12 13:41, Ayal Baron wrote:
>
>
> ----- Original Message -----
>> On 02/02/12 10:57, Laszlo Hornyak wrote:
>>> Hi,
>>>
>>> Yes, the ovirt backend does not shut down or power up any hosts
>>> directly, it can work only through vdsm. Therefore you need one
>>> running host per datacenter to be able to manage the rest of the
>>> hosts.
>>>
>>> I understand the motivation, but for smaller installations I
>>> believe it would be so great if the backend could do it as well.
>>> What vdsm does in the background is not much more than calling
>>> the
>>> ipmipower command.
>>>
>>
>> I agree, there is no real reason not to fence hosts from the
>> management
>> host, yet another feature we would love to have.
>>
>> Worth checking if the engine can reuse the vdsm code for fencing.
>
> This would come for free once we have the all in one (vdsm running
> on the same host as engine).
We'll get it for 'free' when installing VDSM on the same host as the
engine, but the above can be useful even if the user don't install
VDSM
on the engine machine.
I was suggesting that vdsm always be installed on the same host as there are other such
services that the engine could benefit from...
>
>>
>>
>>> Laszlo
>>>
>>> ----- Original Message -----
>>>> From: "Perry Myers" <pmyers(a)redhat.com>
>>>> To: "Spyro Polymiadis" <spyro(a)rsp.com.au>
>>>> Cc: users(a)ovirt.org
>>>> Sent: Thursday, February 2, 2012 4:16:12 AM
>>>> Subject: Re: [Users] Power Management question
>>>>
>>>> On 02/01/2012 10:13 PM, Spyro Polymiadis wrote:
>>>>> so, if i read that right - does this mean that i need to have 2
>>>>> nodes
>>>>> in the cluster to get this working (thats the only difference
>>>>> from
>>>>> the rhev environment) i havent moved the other hypervisors into
>>>>> it
>>>>> yet... i figured the manager host could perform the power
>>>>> management..
>>>>
>>>> That's my understanding, but I could be wrong :) The vdsm/oVirt
>>>> Engine
>>>> folks would know better
>>>>
>>>> Try moving a 2nd host over and see if that resolves the issue
>>>> _______________________________________________
>>>> Users mailing list
>>>> Users(a)ovirt.org
>>>> http://lists.ovirt.org/mailman/listinfo/users
>>>>
>>> _______________________________________________
>>> Users mailing list
>>> Users(a)ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/users
>>
>> _______________________________________________
>> Users mailing list
>> Users(a)ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
5 p.m.
----- Original Message -----
From: "Ayal Baron" <abaron(a)redhat.com>
To: "Livnat Peer" <lpeer(a)redhat.com>
Cc: users(a)ovirt.org, "Laszlo Hornyak" <lhornyak(a)redhat.com>
Sent: Thursday, February 2, 2012 12:54:22 PM
Subject: Re: [Users] Power Management question
----- Original Message -----
> On 02/02/12 13:41, Ayal Baron wrote:
> >
> >
> > ----- Original Message -----
> >> On 02/02/12 10:57, Laszlo Hornyak wrote:
> >>> Hi,
> >>>
> >>> Yes, the ovirt backend does not shut down or power up any hosts
> >>> directly, it can work only through vdsm. Therefore you need one
> >>> running host per datacenter to be able to manage the rest of
> >>> the
> >>> hosts.
> >>>
> >>> I understand the motivation, but for smaller installations I
> >>> believe it would be so great if the backend could do it as
> >>> well.
> >>> What vdsm does in the background is not much more than calling
> >>> the
> >>> ipmipower command.
> >>>
> >>
> >> I agree, there is no real reason not to fence hosts from the
> >> management
> >> host, yet another feature we would love to have.
> >>
> >> Worth checking if the engine can reuse the vdsm code for
> >> fencing.
> >
> > This would come for free once we have the all in one (vdsm
> > running
> > on the same host as engine).
>
> We'll get it for 'free' when installing VDSM on the same host as
> the
> engine, but the above can be useful even if the user don't install
> VDSM
> on the engine machine.
I was suggesting that vdsm always be installed on the same host as
there are other such services that the engine could benefit from...
Yeah, that may be an easy solution, we could just use the vdsClient to run commands in
local, but that would also bring all of vdsm's dependencies, like libvirt to the
engine node. Or maybe the fence-agents package could be enough?
>
> >
> >>
> >>
> >>> Laszlo
> >>>
> >>> ----- Original Message -----
> >>>> From: "Perry Myers" <pmyers(a)redhat.com>
> >>>> To: "Spyro Polymiadis" <spyro(a)rsp.com.au>
> >>>> Cc: users(a)ovirt.org
> >>>> Sent: Thursday, February 2, 2012 4:16:12 AM
> >>>> Subject: Re: [Users] Power Management question
> >>>>
> >>>> On 02/01/2012 10:13 PM, Spyro Polymiadis wrote:
> >>>>> so, if i read that right - does this mean that i need to have
> >>>>> 2
> >>>>> nodes
> >>>>> in the cluster to get this working (thats the only difference
> >>>>> from
> >>>>> the rhev environment) i havent moved the other hypervisors
> >>>>> into
> >>>>> it
> >>>>> yet... i figured the manager host could perform the power
> >>>>> management..
> >>>>
> >>>> That's my understanding, but I could be wrong :) The
> >>>> vdsm/oVirt
> >>>> Engine
> >>>> folks would know better
> >>>>
> >>>> Try moving a 2nd host over and see if that resolves the issue
> >>>> _______________________________________________
> >>>> Users mailing list
> >>>> Users(a)ovirt.org
> >>>> http://lists.ovirt.org/mailman/listinfo/users
> >>>>
> >>> _______________________________________________
> >>> Users mailing list
> >>> Users(a)ovirt.org
> >>> http://lists.ovirt.org/mailman/listinfo/users
> >>
> >> _______________________________________________
> >> Users mailing list
> >> Users(a)ovirt.org
> >> http://lists.ovirt.org/mailman/listinfo/users
> >>
>
>
3:43 a.m.
perfect - confirmed that adding the 2nd host to the cluster enabled me to configure the
power management options :) thanks a bunch
----- Original Message -----
From: "Perry Myers" <pmyers(a)redhat.com>
To: "Spyro Polymiadis" <spyro(a)rsp.com.au>
Cc: users(a)ovirt.org
Sent: Thursday, 2 February, 2012 1:46:12 PM
Subject: Re: [Users] Power Management question
On 02/01/2012 10:13 PM, Spyro Polymiadis wrote:
so, if i read that right - does this mean that i need to have 2
nodes
in the cluster to get this working (thats the only difference from
the rhev environment) i havent moved the other hypervisors into it
yet... i figured the manager host could perform the power
management..
That's my understanding, but I could be wrong :) The vdsm/oVirt Engine
folks would know better
Try moving a 2nd host over and see if that resolves the issue
4689
days inactive
4689
days old
10 comments
5 participants
participants (5)
-
Ayal Baron -
Laszlo Hornyak -
Livnat Peer -
Perry Myers -
Spyro Polymiadis