Re: [Users] Instructions to add a remote controlled power strip not in the native list?

2014-04-08 Thread Eli Mesika


- Original Message -
 From: David Smith dsm...@mypchelp.com
 To: Itamar Heim ih...@redhat.com
 Cc: Marek Grac mg...@redhat.com, Eli Mesika emes...@redhat.com, 
 users users@ovirt.org
 Sent: Monday, April 7, 2014 7:24:35 PM
 Subject: Re: [Users] Instructions to add a remote controlled power strip not 
 in the native list?
 
 Hi Itamar,
 Looks like the Raritan support has been added to upstream release in
 fence-agents, hopefully we can get this into oVirt next.

Good news :-)
Can you please share the final changes you had made to the DB vdc_config 
entries to get this work?
Thanks
Eli

 
  [Bug 519731] Fencing Agent for Raritan devices
 
 Inbox
 
 x
 
   bugzi...@redhat.com
 
 5:32 AM (3 hours ago)
 
to me
 
   https://bugzilla.redhat.com/show_bug.cgi?id=519731
 
 
 
 --- Comment #23 from Marek Grac mg...@redhat.com ---
 Support for Raritan is now part of upstream release - 4.0.8
 
 
 On Mon, Feb 17, 2014 at 5:43 AM, Itamar Heim ih...@redhat.com wrote:
 
  On 02/17/2014 03:31 PM, Marek Grac wrote:
 
  On 02/17/2014 09:45 AM, Eli Mesika wrote:
 
 
  - Original Message -
 
  From: Yedidyah Bar David d...@redhat.com
  To: Itamar Heim ih...@redhat.com
  Cc: users@ovirt.org
  Sent: Sunday, February 16, 2014 2:58:35 PM
  Subject: Re: [Users] Instructions to add a remote controlled power
  strip not in the native list?
 
  - Original Message -
 
  From: Itamar Heim ih...@redhat.com
  To: David Smith dsm...@mypchelp.com, users@ovirt.org
  Sent: Saturday, February 15, 2014 2:57:00 AM
  Subject: Re: [Users] Instructions to add a remote controlled power
  strip
  not in the native list?
 
  On 02/14/2014 07:37 PM, David Smith wrote:
 
  We use Raritan / Dominion PX remote power blocks, is there a way to
  easily add support for these?
 
  CCing Marek on that in case that he had something to add from the
  fence-agents view since it may be already supported implicitly (like
  drac7 that is using actually ipmilan)
 
 
  No, Raritan are not supported yet (rhbz#519731)
 
 
  so david, if you can try to push the raritan support to fence-agents, the
  ovirt side is usually just a config change.
 
 
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] Instructions to add a remote controlled power strip not in the native list?

2014-04-08 Thread Itamar Heim

On 04/08/2014 04:48 PM, Eli Mesika wrote:



- Original Message -

From: David Smith dsm...@mypchelp.com
To: Itamar Heim ih...@redhat.com
Cc: Marek Grac mg...@redhat.com, Eli Mesika emes...@redhat.com, users 
users@ovirt.org
Sent: Monday, April 7, 2014 7:24:35 PM
Subject: Re: [Users] Instructions to add a remote controlled power strip not in 
the native list?

Hi Itamar,
Looks like the Raritan support has been added to upstream release in
fence-agents, hopefully we can get this into oVirt next.


Good news :-)
Can you please share the final changes you had made to the DB vdc_config 
entries to get this work?
Thanks


we still can't distinguish at feature level by hypervisor support.
so adding this to engine will fail for any .el6 distro, until/if this is 
added to rhel 6.6, etc.



Eli



  [Bug 519731] Fencing Agent for Raritan devices

Inbox

x

   bugzi...@redhat.com

5:32 AM (3 hours ago)

to me

   https://bugzilla.redhat.com/show_bug.cgi?id=519731



--- Comment #23 from Marek Grac mg...@redhat.com ---
Support for Raritan is now part of upstream release - 4.0.8


On Mon, Feb 17, 2014 at 5:43 AM, Itamar Heim ih...@redhat.com wrote:


On 02/17/2014 03:31 PM, Marek Grac wrote:


On 02/17/2014 09:45 AM, Eli Mesika wrote:



- Original Message -


From: Yedidyah Bar David d...@redhat.com
To: Itamar Heim ih...@redhat.com
Cc: users@ovirt.org
Sent: Sunday, February 16, 2014 2:58:35 PM
Subject: Re: [Users] Instructions to add a remote controlled power
strip not in the native list?

- Original Message -


From: Itamar Heim ih...@redhat.com
To: David Smith dsm...@mypchelp.com, users@ovirt.org
Sent: Saturday, February 15, 2014 2:57:00 AM
Subject: Re: [Users] Instructions to add a remote controlled power
strip
not in the native list?

On 02/14/2014 07:37 PM, David Smith wrote:


We use Raritan / Dominion PX remote power blocks, is there a way to
easily add support for these?


CCing Marek on that in case that he had something to add from the

fence-agents view since it may be already supported implicitly (like
drac7 that is using actually ipmilan)



No, Raritan are not supported yet (rhbz#519731)



so david, if you can try to push the raritan support to fence-agents, the
ovirt side is usually just a config change.





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


Re: [Users] Instructions to add a remote controlled power strip not in the native list?

2014-04-08 Thread Marek Grac

On 04/08/2014 05:17 PM, Itamar Heim wrote:


we still can't distinguish at feature level by hypervisor support.
so adding this to engine will fail for any .el6 distro, until/if this 
is added to rhel 6.6, etc.

[internal]

Support for Raritan will not be added to rhel6.6/rhel7 until our QA will 
have access to this device for testing (or partner will test it for us). 
We do not have such criteria for upstream.


m,





Eli



  [Bug 519731] Fencing Agent for Raritan devices

Inbox

x

   bugzi...@redhat.com

5:32 AM (3 hours ago)

to me

   https://bugzilla.redhat.com/show_bug.cgi?id=519731



--- Comment #23 from Marek Grac mg...@redhat.com ---
Support for Raritan is now part of upstream release - 4.0.8


On Mon, Feb 17, 2014 at 5:43 AM, Itamar Heim ih...@redhat.com wrote:


On 02/17/2014 03:31 PM, Marek Grac wrote:


On 02/17/2014 09:45 AM, Eli Mesika wrote:



- Original Message -


From: Yedidyah Bar David d...@redhat.com
To: Itamar Heim ih...@redhat.com
Cc: users@ovirt.org
Sent: Sunday, February 16, 2014 2:58:35 PM
Subject: Re: [Users] Instructions to add a remote controlled power
strip not in the native list?

- Original Message -


From: Itamar Heim ih...@redhat.com
To: David Smith dsm...@mypchelp.com, users@ovirt.org
Sent: Saturday, February 15, 2014 2:57:00 AM
Subject: Re: [Users] Instructions to add a remote controlled power
strip
not in the native list?

On 02/14/2014 07:37 PM, David Smith wrote:

We use Raritan / Dominion PX remote power blocks, is there a 
way to

easily add support for these?


CCing Marek on that in case that he had something to add from the

fence-agents view since it may be already supported implicitly (like
drac7 that is using actually ipmilan)



No, Raritan are not supported yet (rhbz#519731)



so david, if you can try to push the raritan support to 
fence-agents, the

ovirt side is usually just a config change.







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


Re: [Users] Instructions to add a remote controlled power strip not in the native list?

2014-04-08 Thread Itamar Heim

On 04/08/2014 08:10 PM, Marek Grac wrote:

On 04/08/2014 05:17 PM, Itamar Heim wrote:


we still can't distinguish at feature level by hypervisor support.
so adding this to engine will fail for any .el6 distro, until/if this
is added to rhel 6.6, etc.

[internal]

Support for Raritan will not be added to rhel6.6/rhel7 until our QA will
have access to this device for testing (or partner will test it for us).
We do not have such criteria for upstream.



Eli/Barak - thoughts on how to resolve this?


m,





Eli



  [Bug 519731] Fencing Agent for Raritan devices

Inbox

x

   bugzi...@redhat.com

5:32 AM (3 hours ago)

to me

   https://bugzilla.redhat.com/show_bug.cgi?id=519731



--- Comment #23 from Marek Grac mg...@redhat.com ---
Support for Raritan is now part of upstream release - 4.0.8


On Mon, Feb 17, 2014 at 5:43 AM, Itamar Heim ih...@redhat.com wrote:


On 02/17/2014 03:31 PM, Marek Grac wrote:


On 02/17/2014 09:45 AM, Eli Mesika wrote:



- Original Message -


From: Yedidyah Bar David d...@redhat.com
To: Itamar Heim ih...@redhat.com
Cc: users@ovirt.org
Sent: Sunday, February 16, 2014 2:58:35 PM
Subject: Re: [Users] Instructions to add a remote controlled power
strip not in the native list?

- Original Message -


From: Itamar Heim ih...@redhat.com
To: David Smith dsm...@mypchelp.com, users@ovirt.org
Sent: Saturday, February 15, 2014 2:57:00 AM
Subject: Re: [Users] Instructions to add a remote controlled power
strip
not in the native list?

On 02/14/2014 07:37 PM, David Smith wrote:


We use Raritan / Dominion PX remote power blocks, is there a
way to
easily add support for these?


CCing Marek on that in case that he had something to add from the

fence-agents view since it may be already supported implicitly (like
drac7 that is using actually ipmilan)



No, Raritan are not supported yet (rhbz#519731)



so david, if you can try to push the raritan support to
fence-agents, the
ovirt side is usually just a config change.









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


Re: [Users] Instructions to add a remote controlled power strip not in the native list?

2014-04-07 Thread David Smith
Hi Itamar,
Looks like the Raritan support has been added to upstream release in
fence-agents, hopefully we can get this into oVirt next.

 [Bug 519731] Fencing Agent for Raritan devices

Inbox

x

  bugzi...@redhat.com

5:32 AM (3 hours ago)

   to me

  https://bugzilla.redhat.com/show_bug.cgi?id=519731



--- Comment #23 from Marek Grac mg...@redhat.com ---
Support for Raritan is now part of upstream release - 4.0.8


On Mon, Feb 17, 2014 at 5:43 AM, Itamar Heim ih...@redhat.com wrote:

 On 02/17/2014 03:31 PM, Marek Grac wrote:

 On 02/17/2014 09:45 AM, Eli Mesika wrote:


 - Original Message -

 From: Yedidyah Bar David d...@redhat.com
 To: Itamar Heim ih...@redhat.com
 Cc: users@ovirt.org
 Sent: Sunday, February 16, 2014 2:58:35 PM
 Subject: Re: [Users] Instructions to add a remote controlled power
 strip not in the native list?

 - Original Message -

 From: Itamar Heim ih...@redhat.com
 To: David Smith dsm...@mypchelp.com, users@ovirt.org
 Sent: Saturday, February 15, 2014 2:57:00 AM
 Subject: Re: [Users] Instructions to add a remote controlled power
 strip
 not in the native list?

 On 02/14/2014 07:37 PM, David Smith wrote:

 We use Raritan / Dominion PX remote power blocks, is there a way to
 easily add support for these?

 CCing Marek on that in case that he had something to add from the
 fence-agents view since it may be already supported implicitly (like
 drac7 that is using actually ipmilan)


 No, Raritan are not supported yet (rhbz#519731)


 so david, if you can try to push the raritan support to fence-agents, the
 ovirt side is usually just a config change.

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


Re: [Users] Instructions to add a remote controlled power strip not in the native list?

2014-03-26 Thread Marek Grac

On 03/25/2014 07:37 PM, David Smith wrote:


Unfortunately it looks like fencing.py is where the legacy --option 
was translated to --action. I believe ovirt calls fencing.py as a 
proxy to execute fence_raritan?


The version of fence-agents I pulled from git has the backwards 
compatibility removed;
https://lists.fedorahosted.org/pipermail/cluster-commits/2013-February/003090.html 



So if I added support for it in fence_raritan I'm not sure it would 
work (I can try) but also the fence-agents guys probably wouldn't take 
the submission to have it added to future code.


Those legacy options where completely removed from v4.0 - there is an 
another branch v3.9.x which is based on new code but with all legacy 
options, it is possible that it will be one day ported to RHEL6 but it 
is not a priority right now.


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


Re: [Users] Instructions to add a remote controlled power strip not in the native list?

2014-03-26 Thread David Smith
Ok, well I hope the latest submission I sent in to the fence-agents group
gets approved and can get added in sooner than later.

In any case, I've got everything up and running now :-)


On Wed, Mar 26, 2014 at 1:34 AM, Marek Grac mg...@redhat.com wrote:

 On 03/25/2014 07:37 PM, David Smith wrote:


 Unfortunately it looks like fencing.py is where the legacy --option was
 translated to --action. I believe ovirt calls fencing.py as a proxy to
 execute fence_raritan?

 The version of fence-agents I pulled from git has the backwards
 compatibility removed;
 https://lists.fedorahosted.org/pipermail/cluster-commits/
 2013-February/003090.html

 So if I added support for it in fence_raritan I'm not sure it would work
 (I can try) but also the fence-agents guys probably wouldn't take the
 submission to have it added to future code.

  Those legacy options where completely removed from v4.0 - there is an
 another branch v3.9.x which is based on new code but with all legacy
 options, it is possible that it will be one day ported to RHEL6 but it is
 not a priority right now.

 m,

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


Re: [Users] Instructions to add a remote controlled power strip not in the native list?

2014-03-25 Thread Eli Mesika


- Original Message -
 From: David Smith dsm...@mypchelp.com
 To: Eli Mesika emes...@redhat.com
 Cc: Marek Grac mg...@redhat.com, users users@ovirt.org, Yedidyah Bar 
 David d...@redhat.com
 Sent: Tuesday, March 25, 2014 3:04:53 AM
 Subject: Re: [Users] Instructions to add a remote controlled power strip not 
 in the native list?
 
 All right, serious progress. Thanks to all for your nudges in the right
 direction.
 I've managed to get my ovirt to recognize and use the agent.
 I have a new problem however
 
 I get this message when the fence_raritan agent is run: Ignoring unknown
 option 'option=status' fence
 So it appears that my fence_raritan agent is being sent --option instead
 of --action
 
 Since the default behavior is reboot (fence_raritan expects --action= not
 --option=) the systems reboot every time a status request is sent :( hehe
 
 Related:? https://bugzilla.redhat.com/show_bug.cgi?id=987446
 I'm not using concurrent

Not related 

 
 So the question is, does anyone here know what the best course of action to
 resolve this issue is?  My host machines are running centos 6.5.
 Is this problem within a fencing package, ovirt, or other?

AFAIK this is related to http://gerrit.ovirt.org/#/c/24343/ which changed 
--option to --action 
danken ?

 
 I tried to set option=action in the engine database, but it appears theres
 probably only a few (3?) mappings possible there, unless I'm wrong and
 there are more?
 
 
 This is what I've changed for now, using 3.3 cluster;
 UPDATE vdc_options SET
 option_value='apc:secure=secure,port=ipport,slot=port;apc_snmp:port=port;bladecenter:secure=secure,port=ipport,slot=port;cisco_ucs:secure=ssl,slot=port;drac5:secure=secure,slot=port;eps:slot=port;ilo:secure=ssl,port=ipport;ipmilan:;ilo2:secure=ssl,port=ipport;ilo3:;ilo4:;rsa:secure=secure,port=ipport;rsb:;wti:secure=secure,port=ipport,slot=port;raritan:slot=port,port=ipport;'
 where option_id=389;
 
 UPDATE vdc_options SET
 option_value='apc,apc_snmp,bladecenter,cisco_ucs,drac5,eps,ilo,ilo2,ilo3,ilo4,ipmilan,rsa,rsb,wti,raritan'
 where option_id=395;
 
 
 On Mon, Mar 24, 2014 at 2:07 PM, Eli Mesika emes...@redhat.com wrote:
 
 
 
  - Original Message -
   From: David Smith dsm...@mypchelp.com
   To: Eli Mesika emes...@redhat.com
   Cc: Marek Grac mg...@redhat.com, users users@ovirt.org,
  Yedidyah Bar David d...@redhat.com
   Sent: Friday, March 21, 2014 4:33:17 PM
   Subject: Re: [Users] Instructions to add a remote controlled power strip
  not in the native list?
  
   Hey guys,
  
   I submitted an initial agent for raritan to the fence-agents group,
  however
   I have a feeling after experimenting with the ipmilan agent that my agent
   won't work with oVirt;
 
  Can you please elaborate on that ? what will not work and why this is
  related to the ipmilan card ?
 
  
   Is the command set for each agent determined by the oVirt database
  itself,
   in other words, when I add the agent the abilities are then added?
 
  Please see http://www.ovirt.org/Custom_Fencing for the exact set of
  fields in database involved in that.
  If you are implementing raritan PM agent , you should have fence_raritan
  in /usr/sbin of the host that is selected as a proxy for the fencing
  operation, you should also make sure that this script has similar
  permissions as other scripts bundled with the fence-agents RPM
 
  
   For example the agent I submitted only has support for connectivity
   settings and power on/off/reboot as well as some delays. Also currently
  it
   requires that the port be specified as a path ie /system1/outlet1
  
   Will this work as an outlet path?
 
  You can try to put that in the options field in the UI for the PM agent
  definition , i.e port=/system1/outlet1
 
   Minimum commands required to work?
 
  Not sure I go you here , please elaborate/explain
 
  
   Thanks
  
 
 
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] Instructions to add a remote controlled power strip not in the native list?

2014-03-25 Thread David Smith
Hehe. Apparently not, unless I pulled an old copy of fence-agents somehow
direct from git? I used the master branch too.


On Tue, Mar 25, 2014 at 2:46 AM, Eli Mesika emes...@redhat.com wrote:



 - Original Message -
  From: David Smith dsm...@mypchelp.com
  To: Eli Mesika emes...@redhat.com
  Cc: Marek Grac mg...@redhat.com, users users@ovirt.org,
 Yedidyah Bar David d...@redhat.com
  Sent: Tuesday, March 25, 2014 3:04:53 AM
  Subject: Re: [Users] Instructions to add a remote controlled power strip
 not in the native list?
 
  All right, serious progress. Thanks to all for your nudges in the right
  direction.
  I've managed to get my ovirt to recognize and use the agent.
  I have a new problem however
 
  I get this message when the fence_raritan agent is run: Ignoring unknown
  option 'option=status' fence
  So it appears that my fence_raritan agent is being sent --option
 instead
  of --action
 
  Since the default behavior is reboot (fence_raritan expects --action=
 not
  --option=) the systems reboot every time a status request is sent :( hehe
 
  Related:? https://bugzilla.redhat.com/show_bug.cgi?id=987446
  I'm not using concurrent

 Not related

 
  So the question is, does anyone here know what the best course of action
 to
  resolve this issue is?  My host machines are running centos 6.5.
  Is this problem within a fencing package, ovirt, or other?

 AFAIK this is related to http://gerrit.ovirt.org/#/c/24343/ which changed
 --option to --action
 danken ?

 
  I tried to set option=action in the engine database, but it appears
 theres
  probably only a few (3?) mappings possible there, unless I'm wrong and
  there are more?
 
 
  This is what I've changed for now, using 3.3 cluster;
  UPDATE vdc_options SET
 
 option_value='apc:secure=secure,port=ipport,slot=port;apc_snmp:port=port;bladecenter:secure=secure,port=ipport,slot=port;cisco_ucs:secure=ssl,slot=port;drac5:secure=secure,slot=port;eps:slot=port;ilo:secure=ssl,port=ipport;ipmilan:;ilo2:secure=ssl,port=ipport;ilo3:;ilo4:;rsa:secure=secure,port=ipport;rsb:;wti:secure=secure,port=ipport,slot=port;raritan:slot=port,port=ipport;'
  where option_id=389;
 
  UPDATE vdc_options SET
 
 option_value='apc,apc_snmp,bladecenter,cisco_ucs,drac5,eps,ilo,ilo2,ilo3,ilo4,ipmilan,rsa,rsb,wti,raritan'
  where option_id=395;
 
 
  On Mon, Mar 24, 2014 at 2:07 PM, Eli Mesika emes...@redhat.com wrote:
 
  
  
   - Original Message -
From: David Smith dsm...@mypchelp.com
To: Eli Mesika emes...@redhat.com
Cc: Marek Grac mg...@redhat.com, users users@ovirt.org,
   Yedidyah Bar David d...@redhat.com
Sent: Friday, March 21, 2014 4:33:17 PM
Subject: Re: [Users] Instructions to add a remote controlled power
 strip
   not in the native list?
   
Hey guys,
   
I submitted an initial agent for raritan to the fence-agents group,
   however
I have a feeling after experimenting with the ipmilan agent that my
 agent
won't work with oVirt;
  
   Can you please elaborate on that ? what will not work and why this is
   related to the ipmilan card ?
  
   
Is the command set for each agent determined by the oVirt database
   itself,
in other words, when I add the agent the abilities are then added?
  
   Please see http://www.ovirt.org/Custom_Fencing for the exact set of
   fields in database involved in that.
   If you are implementing raritan PM agent , you should have
 fence_raritan
   in /usr/sbin of the host that is selected as a proxy for the fencing
   operation, you should also make sure that this script has similar
   permissions as other scripts bundled with the fence-agents RPM
  
   
For example the agent I submitted only has support for connectivity
settings and power on/off/reboot as well as some delays. Also
 currently
   it
requires that the port be specified as a path ie /system1/outlet1
   
Will this work as an outlet path?
  
   You can try to put that in the options field in the UI for the PM agent
   definition , i.e port=/system1/outlet1
  
Minimum commands required to work?
  
   Not sure I go you here , please elaborate/explain
  
   
Thanks
   
  
 

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


Re: [Users] Instructions to add a remote controlled power strip not in the native list?

2014-03-25 Thread David Smith
oh I see, since I have the latest fence, that's where option is now
missing, got it.. just a minor tweak to api.py ;)


On Tue, Mar 25, 2014 at 8:25 AM, David Smith dsm...@mypchelp.com wrote:

 Hehe. Apparently not, unless I pulled an old copy of fence-agents somehow
 direct from git? I used the master branch too.


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


Re: [Users] Instructions to add a remote controlled power strip not in the native list?

2014-03-25 Thread David Smith
Eli,

I changed the line in API.py and ran py_compile to obtain API.pyc and pyo
files, copied them to all hypervisors, and I'm still getting option=status..

Did I miss something else?

Thread-199071::DEBUG::2014-03-25 10:28:10,587::API::1110::vds::(fenceNode)
fenceNode(addr=10.105.128.25,port=,agent=raritan,user=admin,passwd=,action=s
tatus,secure=,options=port=/system1/outlet6)


Thread-199071::DEBUG::2014-03-25 10:28:13,104::API::1136::vds::(fenceNode)
rc 0 in agent=fence_raritan
ipaddr=10.105.128.25
login=admin
option=status
passwd=
port=/system1/outlet6 out Success: Rebooted
 err Parse error: Ignoring unknown option 'option=status'

Looks like in the first command the option was indeed changed to
action=status but the return status showed option=status was used?



On Tue, Mar 25, 2014 at 2:46 AM, Eli Mesika emes...@redhat.com wrote:



 - Original Message -
  From: David Smith dsm...@mypchelp.com
  To: Eli Mesika emes...@redhat.com
  Cc: Marek Grac mg...@redhat.com, users users@ovirt.org,
 Yedidyah Bar David d...@redhat.com
  Sent: Tuesday, March 25, 2014 3:04:53 AM
  Subject: Re: [Users] Instructions to add a remote controlled power strip
 not in the native list?
 
  All right, serious progress. Thanks to all for your nudges in the right
  direction.
  I've managed to get my ovirt to recognize and use the agent.
  I have a new problem however
 
  I get this message when the fence_raritan agent is run: Ignoring unknown
  option 'option=status' fence
  So it appears that my fence_raritan agent is being sent --option
 instead
  of --action
 
  Since the default behavior is reboot (fence_raritan expects --action=
 not
  --option=) the systems reboot every time a status request is sent :( hehe
 
  Related:? https://bugzilla.redhat.com/show_bug.cgi?id=987446
  I'm not using concurrent

 Not related

 
  So the question is, does anyone here know what the best course of action
 to
  resolve this issue is?  My host machines are running centos 6.5.
  Is this problem within a fencing package, ovirt, or other?

 AFAIK this is related to http://gerrit.ovirt.org/#/c/24343/ which changed
 --option to --action
 danken ?

 
  I tried to set option=action in the engine database, but it appears
 theres
  probably only a few (3?) mappings possible there, unless I'm wrong and
  there are more?
 
 
  This is what I've changed for now, using 3.3 cluster;
  UPDATE vdc_options SET
 
 option_value='apc:secure=secure,port=ipport,slot=port;apc_snmp:port=port;bladecenter:secure=secure,port=ipport,slot=port;cisco_ucs:secure=ssl,slot=port;drac5:secure=secure,slot=port;eps:slot=port;ilo:secure=ssl,port=ipport;ipmilan:;ilo2:secure=ssl,port=ipport;ilo3:;ilo4:;rsa:secure=secure,port=ipport;rsb:;wti:secure=secure,port=ipport,slot=port;raritan:slot=port,port=ipport;'
  where option_id=389;
 
  UPDATE vdc_options SET
 
 option_value='apc,apc_snmp,bladecenter,cisco_ucs,drac5,eps,ilo,ilo2,ilo3,ilo4,ipmilan,rsa,rsb,wti,raritan'
  where option_id=395;
 
 
  On Mon, Mar 24, 2014 at 2:07 PM, Eli Mesika emes...@redhat.com wrote:
 
  
  
   - Original Message -
From: David Smith dsm...@mypchelp.com
To: Eli Mesika emes...@redhat.com
Cc: Marek Grac mg...@redhat.com, users users@ovirt.org,
   Yedidyah Bar David d...@redhat.com
Sent: Friday, March 21, 2014 4:33:17 PM
Subject: Re: [Users] Instructions to add a remote controlled power
 strip
   not in the native list?
   
Hey guys,
   
I submitted an initial agent for raritan to the fence-agents group,
   however
I have a feeling after experimenting with the ipmilan agent that my
 agent
won't work with oVirt;
  
   Can you please elaborate on that ? what will not work and why this is
   related to the ipmilan card ?
  
   
Is the command set for each agent determined by the oVirt database
   itself,
in other words, when I add the agent the abilities are then added?
  
   Please see http://www.ovirt.org/Custom_Fencing for the exact set of
   fields in database involved in that.
   If you are implementing raritan PM agent , you should have
 fence_raritan
   in /usr/sbin of the host that is selected as a proxy for the fencing
   operation, you should also make sure that this script has similar
   permissions as other scripts bundled with the fence-agents RPM
  
   
For example the agent I submitted only has support for connectivity
settings and power on/off/reboot as well as some delays. Also
 currently
   it
requires that the port be specified as a path ie /system1/outlet1
   
Will this work as an outlet path?
  
   You can try to put that in the options field in the UI for the PM agent
   definition , i.e port=/system1/outlet1
  
Minimum commands required to work?
  
   Not sure I go you here , please elaborate/explain
  
   
Thanks
   
  
 

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


Re: [Users] Instructions to add a remote controlled power strip not in the native list?

2014-03-25 Thread Dan Kenigsberg
On Tue, Mar 25, 2014 at 09:00:42AM -0700, David Smith wrote:
 oh I see, since I have the latest fence, that's where option is now
 missing, got it.. just a minor tweak to api.py ;)
 
 
 On Tue, Mar 25, 2014 at 8:25 AM, David Smith dsm...@mypchelp.com wrote:
 
  Hehe. Apparently not, unless I pulled an old copy of fence-agents somehow
  direct from git? I used the master branch too.
 
 

Is there any reason for you not to use the pre-packaged fence-agents?
I am not very happy about intoducing non-necessary changes to
old stable branches like ovirt-3.3. To do this, I'd need a BZ opened,
explaining why this is actually a good thing.

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


Re: [Users] Instructions to add a remote controlled power strip not in the native list?

2014-03-25 Thread David Smith
Yes, they don't have support for raritan. I'm working on getting the
fence-agents guys to accept my new code, however, I'm also testing it by
getting it working into oVirt 3.3 (since that's what I've got installed and
working)

Thanks!


On Tue, Mar 25, 2014 at 10:28 AM, Dan Kenigsberg dan...@redhat.com wrote:

 On Tue, Mar 25, 2014 at 09:00:42AM -0700, David Smith wrote:
  oh I see, since I have the latest fence, that's where option is now
  missing, got it.. just a minor tweak to api.py ;)
 
 
  On Tue, Mar 25, 2014 at 8:25 AM, David Smith dsm...@mypchelp.com
 wrote:
 
   Hehe. Apparently not, unless I pulled an old copy of fence-agents
 somehow
   direct from git? I used the master branch too.
  
  

 Is there any reason for you not to use the pre-packaged fence-agents?
 I am not very happy about intoducing non-necessary changes to
 old stable branches like ovirt-3.3. To do this, I'd need a BZ opened,
 explaining why this is actually a good thing.

 Regards,
 Dan.

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


Re: [Users] Instructions to add a remote controlled power strip not in the native list?

2014-03-25 Thread Dan Kenigsberg
On Tue, Mar 25, 2014 at 05:46:58AM -0400, Eli Mesika wrote:
 
 
 - Original Message -
  From: David Smith dsm...@mypchelp.com
  To: Eli Mesika emes...@redhat.com
  Cc: Marek Grac mg...@redhat.com, users users@ovirt.org, Yedidyah 
  Bar David d...@redhat.com
  Sent: Tuesday, March 25, 2014 3:04:53 AM
  Subject: Re: [Users] Instructions to add a remote controlled power strip 
  not in the native list?
  
  All right, serious progress. Thanks to all for your nudges in the right
  direction.
  I've managed to get my ovirt to recognize and use the agent.
  I have a new problem however
  
  I get this message when the fence_raritan agent is run: Ignoring unknown
  option 'option=status' fence
  So it appears that my fence_raritan agent is being sent --option instead
  of --action
  
  Since the default behavior is reboot (fence_raritan expects --action= not
  --option=) the systems reboot every time a status request is sent :( hehe
  
  Related:? https://bugzilla.redhat.com/show_bug.cgi?id=987446
  I'm not using concurrent
 
 Not related 
 
  
  So the question is, does anyone here know what the best course of action to
  resolve this issue is?  My host machines are running centos 6.5.
  Is this problem within a fencing package, ovirt, or other?
 
 AFAIK this is related to http://gerrit.ovirt.org/#/c/24343/ which changed 
 --option to --action 
 danken ?

I smells very much related.
Where is fence_raritan comming from? Could you have the el6 version of
it support the legacy --option name?

If not, we could consider taking http://gerrit.ovirt.org/#/c/26075/.

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


Re: [Users] Instructions to add a remote controlled power strip not in the native list?

2014-03-25 Thread David Smith
I created fence_raritan.

Unfortunately it looks like fencing.py is where the legacy --option was
translated to --action. I believe ovirt calls fencing.py as a proxy to
execute fence_raritan?

The version of fence-agents I pulled from git has the backwards
compatibility removed;
https://lists.fedorahosted.org/pipermail/cluster-commits/2013-February/003090.html


So if I added support for it in fence_raritan I'm not sure it would work (I
can try) but also the fence-agents guys probably wouldn't take the
submission to have it added to future code.

I edited API.py as in http://gerrit.ovirt.org/#/c/26075/ and re-compiled
API.py to pyc and pyo files and copied to all my hosts, yet I'm still
getting an error, so I'm wondering if that change is incomplete or I missed
some other step to make this actually work.  It's really a bummer
especially since the default behavior with no action is reboot ;)


*Thread-199071::DEBUG::2014-03-25 10:28:10,587::API::1110::vds::(fenceNode)
fenceNode(addr=10.105.128.25,port=,agent=raritan,user=admin,passwd=,action=status,secure=,options=port=/system1/outlet6)*


*Thread-199071::DEBUG::2014-03-25 10:28:13,104::API::1136::vds::(fenceNode)
rc 0 in agent=fence_raritan*
*ipaddr=10.105.128.25*
*login=admin*
*option=status*
*passwd=*
*port=/system1/outlet6 out Success: Rebooted*
* err Parse error: Ignoring unknown option 'option=status'*


On Tue, Mar 25, 2014 at 6:28 AM, Dan Kenigsberg dan...@redhat.com wrote:

 On Tue, Mar 25, 2014 at 05:46:58AM -0400, Eli Mesika wrote:
  AFAIK this is related to http://gerrit.ovirt.org/#/c/24343/ which
 changed --option to --action
  danken ?

 I smells very much related.
 Where is fence_raritan comming from? Could you have the el6 version of
 it support the legacy --option name?

 If not, we could consider taking http://gerrit.ovirt.org/#/c/26075/.

 Dan.

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


Re: [Users] Instructions to add a remote controlled power strip not in the native list?

2014-03-25 Thread Dan Kenigsberg
On Tue, Mar 25, 2014 at 11:37:13AM -0700, David Smith wrote:
 I created fence_raritan.
 
 Unfortunately it looks like fencing.py is where the legacy --option was
 translated to --action. I believe ovirt calls fencing.py as a proxy to
 execute fence_raritan?
 
 The version of fence-agents I pulled from git has the backwards
 compatibility removed;
 https://lists.fedorahosted.org/pipermail/cluster-commits/2013-February/003090.html
 
 
 So if I added support for it in fence_raritan I'm not sure it would work (I
 can try) but also the fence-agents guys probably wouldn't take the
 submission to have it added to future code.

Indeed - I do not expect upstream fence-agents to accept the legacy
option. However, you could backport your own code to el6, and create a
fence-agents-raritan rpm from it.

 
 I edited API.py as in http://gerrit.ovirt.org/#/c/26075/ and re-compiled
 API.py to pyc and pyo files and copied to all my hosts, yet I'm still
 getting an error, so I'm wondering if that change is incomplete or I missed
 some other step to make this actually work.  It's really a bummer
 especially since the default behavior with no action is reboot ;)

I suppose that you have missed something. My don't you place API.py
under /usr/share/vdsm ? And make sure you restart vdsmd, to make the new
code take effect?

 
 
 *Thread-199071::DEBUG::2014-03-25 10:28:10,587::API::1110::vds::(fenceNode)
 fenceNode(addr=10.105.128.25,port=,agent=raritan,user=admin,passwd=,action=status,secure=,options=port=/system1/outlet6)*
 
 
 *Thread-199071::DEBUG::2014-03-25 10:28:13,104::API::1136::vds::(fenceNode)
 rc 0 in agent=fence_raritan*
 *ipaddr=10.105.128.25*
 *login=admin*
 *option=status*
 *passwd=*
 *port=/system1/outlet6 out Success: Rebooted*
 * err Parse error: Ignoring unknown option 'option=status'*
 
 
 On Tue, Mar 25, 2014 at 6:28 AM, Dan Kenigsberg dan...@redhat.com wrote:
 
  On Tue, Mar 25, 2014 at 05:46:58AM -0400, Eli Mesika wrote:
   AFAIK this is related to http://gerrit.ovirt.org/#/c/24343/ which
  changed --option to --action
   danken ?
 
  I smells very much related.
  Where is fence_raritan comming from? Could you have the el6 version of
  it support the legacy --option name?
 
  If not, we could consider taking http://gerrit.ovirt.org/#/c/26075/.
 
  Dan.
 
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] Instructions to add a remote controlled power strip not in the native list?

2014-03-25 Thread David Smith
Crap, didn't realize I just had to restart vdsm for the new API.py to take
effect.
Anyway I edited fencing.py and added back the compatibility code, and its
all working for now.

I'm going to work on touch up changes on fence_raritan so that we can get
it submitted into the next release hopefully, all of these other hacks will
become moot at that time.


On Tue, Mar 25, 2014 at 2:08 PM, Dan Kenigsberg dan...@redhat.com wrote:

 On Tue, Mar 25, 2014 at 11:37:13AM -0700, David Smith wrote:
  I created fence_raritan.
 
  Unfortunately it looks like fencing.py is where the legacy --option was
  translated to --action. I believe ovirt calls fencing.py as a proxy to
  execute fence_raritan?
 
  The version of fence-agents I pulled from git has the backwards
  compatibility removed;
 
 https://lists.fedorahosted.org/pipermail/cluster-commits/2013-February/003090.html
 
 
  So if I added support for it in fence_raritan I'm not sure it would work
 (I
  can try) but also the fence-agents guys probably wouldn't take the
  submission to have it added to future code.

 Indeed - I do not expect upstream fence-agents to accept the legacy
 option. However, you could backport your own code to el6, and create a
 fence-agents-raritan rpm from it.

 
  I edited API.py as in http://gerrit.ovirt.org/#/c/26075/ and re-compiled
  API.py to pyc and pyo files and copied to all my hosts, yet I'm still
  getting an error, so I'm wondering if that change is incomplete or I
 missed
  some other step to make this actually work.  It's really a bummer
  especially since the default behavior with no action is reboot ;)

 I suppose that you have missed something. My don't you place API.py
 under /usr/share/vdsm ? And make sure you restart vdsmd, to make the new
 code take effect?

 
 
  *Thread-199071::DEBUG::2014-03-25
 10:28:10,587::API::1110::vds::(fenceNode)
 
 fenceNode(addr=10.105.128.25,port=,agent=raritan,user=admin,passwd=,action=status,secure=,options=port=/system1/outlet6)*
 
 
  *Thread-199071::DEBUG::2014-03-25
 10:28:13,104::API::1136::vds::(fenceNode)
  rc 0 in agent=fence_raritan*
  *ipaddr=10.105.128.25*
  *login=admin*
  *option=status*
  *passwd=*
  *port=/system1/outlet6 out Success: Rebooted*
  * err Parse error: Ignoring unknown option 'option=status'*
 
 
  On Tue, Mar 25, 2014 at 6:28 AM, Dan Kenigsberg dan...@redhat.com
 wrote:
 
   On Tue, Mar 25, 2014 at 05:46:58AM -0400, Eli Mesika wrote:
AFAIK this is related to http://gerrit.ovirt.org/#/c/24343/ which
   changed --option to --action
danken ?
  
   I smells very much related.
   Where is fence_raritan comming from? Could you have the el6 version of
   it support the legacy --option name?
  
   If not, we could consider taking http://gerrit.ovirt.org/#/c/26075/.
  
   Dan.
  

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


Re: [Users] Instructions to add a remote controlled power strip not in the native list?

2014-03-25 Thread Eli Mesika


- Original Message -
 From: David Smith dsm...@mypchelp.com
 To: Dan Kenigsberg dan...@redhat.com
 Cc: Eli Mesika emes...@redhat.com, Marek Grac mg...@redhat.com, 
 users users@ovirt.org, Yedidyah Bar
 David d...@redhat.com
 Sent: Tuesday, March 25, 2014 11:36:16 PM
 Subject: Re: [Users] Instructions to add a remote controlled power strip not 
 in the native list?
 
 Crap, didn't realize I just had to restart vdsm for the new API.py to take
 effect.
 Anyway I edited fencing.py and added back the compatibility code, and its
 all working for now.

Good news :-)

 
 I'm going to work on touch up changes on fence_raritan so that we can get
 it submitted into the next release hopefully, all of these other hacks will
 become moot at that time.
 
 
 On Tue, Mar 25, 2014 at 2:08 PM, Dan Kenigsberg dan...@redhat.com wrote:
 
  On Tue, Mar 25, 2014 at 11:37:13AM -0700, David Smith wrote:
   I created fence_raritan.
  
   Unfortunately it looks like fencing.py is where the legacy --option was
   translated to --action. I believe ovirt calls fencing.py as a proxy to
   execute fence_raritan?
  
   The version of fence-agents I pulled from git has the backwards
   compatibility removed;
  
  https://lists.fedorahosted.org/pipermail/cluster-commits/2013-February/003090.html
  
  
   So if I added support for it in fence_raritan I'm not sure it would work
  (I
   can try) but also the fence-agents guys probably wouldn't take the
   submission to have it added to future code.
 
  Indeed - I do not expect upstream fence-agents to accept the legacy
  option. However, you could backport your own code to el6, and create a
  fence-agents-raritan rpm from it.
 
  
   I edited API.py as in http://gerrit.ovirt.org/#/c/26075/ and re-compiled
   API.py to pyc and pyo files and copied to all my hosts, yet I'm still
   getting an error, so I'm wondering if that change is incomplete or I
  missed
   some other step to make this actually work.  It's really a bummer
   especially since the default behavior with no action is reboot ;)
 
  I suppose that you have missed something. My don't you place API.py
  under /usr/share/vdsm ? And make sure you restart vdsmd, to make the new
  code take effect?
 
  
  
   *Thread-199071::DEBUG::2014-03-25
  10:28:10,587::API::1110::vds::(fenceNode)
  
  fenceNode(addr=10.105.128.25,port=,agent=raritan,user=admin,passwd=,action=status,secure=,options=port=/system1/outlet6)*
  
  
   *Thread-199071::DEBUG::2014-03-25
  10:28:13,104::API::1136::vds::(fenceNode)
   rc 0 in agent=fence_raritan*
   *ipaddr=10.105.128.25*
   *login=admin*
   *option=status*
   *passwd=*
   *port=/system1/outlet6 out Success: Rebooted*
   * err Parse error: Ignoring unknown option 'option=status'*
  
  
   On Tue, Mar 25, 2014 at 6:28 AM, Dan Kenigsberg dan...@redhat.com
  wrote:
  
On Tue, Mar 25, 2014 at 05:46:58AM -0400, Eli Mesika wrote:
 AFAIK this is related to http://gerrit.ovirt.org/#/c/24343/ which
changed --option to --action
 danken ?
   
I smells very much related.
Where is fence_raritan comming from? Could you have the el6 version of
it support the legacy --option name?
   
If not, we could consider taking http://gerrit.ovirt.org/#/c/26075/.
   
Dan.
   
 
 
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] Instructions to add a remote controlled power strip not in the native list?

2014-03-24 Thread Eli Mesika


- Original Message -
 From: David Smith dsm...@mypchelp.com
 To: Eli Mesika emes...@redhat.com
 Cc: Marek Grac mg...@redhat.com, users users@ovirt.org, Yedidyah Bar 
 David d...@redhat.com
 Sent: Friday, March 21, 2014 4:33:17 PM
 Subject: Re: [Users] Instructions to add a remote controlled power strip not 
 in the native list?
 
 Hey guys,
 
 I submitted an initial agent for raritan to the fence-agents group, however
 I have a feeling after experimenting with the ipmilan agent that my agent
 won't work with oVirt;

Can you please elaborate on that ? what will not work and why this is related 
to the ipmilan card ?

 
 Is the command set for each agent determined by the oVirt database itself,
 in other words, when I add the agent the abilities are then added?

Please see http://www.ovirt.org/Custom_Fencing for the exact set of fields in 
database involved in that.
If you are implementing raritan PM agent , you should have fence_raritan in 
/usr/sbin of the host that is selected as a proxy for the fencing operation, 
you should also make sure that this script has similar permissions as other 
scripts bundled with the fence-agents RPM

 
 For example the agent I submitted only has support for connectivity
 settings and power on/off/reboot as well as some delays. Also currently it
 requires that the port be specified as a path ie /system1/outlet1
 
 Will this work as an outlet path?

You can try to put that in the options field in the UI for the PM agent 
definition , i.e port=/system1/outlet1

 Minimum commands required to work?

Not sure I go you here , please elaborate/explain 

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


Re: [Users] Instructions to add a remote controlled power strip not in the native list?

2014-03-24 Thread David Smith
All right, serious progress. Thanks to all for your nudges in the right
direction.
I've managed to get my ovirt to recognize and use the agent.
I have a new problem however

I get this message when the fence_raritan agent is run: Ignoring unknown
option 'option=status' fence
So it appears that my fence_raritan agent is being sent --option instead
of --action

Since the default behavior is reboot (fence_raritan expects --action= not
--option=) the systems reboot every time a status request is sent :( hehe

Related:? https://bugzilla.redhat.com/show_bug.cgi?id=987446
I'm not using concurrent

So the question is, does anyone here know what the best course of action to
resolve this issue is?  My host machines are running centos 6.5.
Is this problem within a fencing package, ovirt, or other?

I tried to set option=action in the engine database, but it appears theres
probably only a few (3?) mappings possible there, unless I'm wrong and
there are more?


This is what I've changed for now, using 3.3 cluster;
UPDATE vdc_options SET
option_value='apc:secure=secure,port=ipport,slot=port;apc_snmp:port=port;bladecenter:secure=secure,port=ipport,slot=port;cisco_ucs:secure=ssl,slot=port;drac5:secure=secure,slot=port;eps:slot=port;ilo:secure=ssl,port=ipport;ipmilan:;ilo2:secure=ssl,port=ipport;ilo3:;ilo4:;rsa:secure=secure,port=ipport;rsb:;wti:secure=secure,port=ipport,slot=port;raritan:slot=port,port=ipport;'
where option_id=389;

UPDATE vdc_options SET
option_value='apc,apc_snmp,bladecenter,cisco_ucs,drac5,eps,ilo,ilo2,ilo3,ilo4,ipmilan,rsa,rsb,wti,raritan'
where option_id=395;


On Mon, Mar 24, 2014 at 2:07 PM, Eli Mesika emes...@redhat.com wrote:



 - Original Message -
  From: David Smith dsm...@mypchelp.com
  To: Eli Mesika emes...@redhat.com
  Cc: Marek Grac mg...@redhat.com, users users@ovirt.org,
 Yedidyah Bar David d...@redhat.com
  Sent: Friday, March 21, 2014 4:33:17 PM
  Subject: Re: [Users] Instructions to add a remote controlled power strip
 not in the native list?
 
  Hey guys,
 
  I submitted an initial agent for raritan to the fence-agents group,
 however
  I have a feeling after experimenting with the ipmilan agent that my agent
  won't work with oVirt;

 Can you please elaborate on that ? what will not work and why this is
 related to the ipmilan card ?

 
  Is the command set for each agent determined by the oVirt database
 itself,
  in other words, when I add the agent the abilities are then added?

 Please see http://www.ovirt.org/Custom_Fencing for the exact set of
 fields in database involved in that.
 If you are implementing raritan PM agent , you should have fence_raritan
 in /usr/sbin of the host that is selected as a proxy for the fencing
 operation, you should also make sure that this script has similar
 permissions as other scripts bundled with the fence-agents RPM

 
  For example the agent I submitted only has support for connectivity
  settings and power on/off/reboot as well as some delays. Also currently
 it
  requires that the port be specified as a path ie /system1/outlet1
 
  Will this work as an outlet path?

 You can try to put that in the options field in the UI for the PM agent
 definition , i.e port=/system1/outlet1

  Minimum commands required to work?

 Not sure I go you here , please elaborate/explain

 
  Thanks
 

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


Re: [Users] Instructions to add a remote controlled power strip not in the native list?

2014-03-21 Thread David Smith
Hey guys,

I submitted an initial agent for raritan to the fence-agents group, however
I have a feeling after experimenting with the ipmilan agent that my agent
won't work with oVirt;

Is the command set for each agent determined by the oVirt database itself,
in other words, when I add the agent the abilities are then added?

For example the agent I submitted only has support for connectivity
settings and power on/off/reboot as well as some delays. Also currently it
requires that the port be specified as a path ie /system1/outlet1

Will this work as an outlet path?
Minimum commands required to work?

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


Re: [Users] Instructions to add a remote controlled power strip not in the native list?

2014-03-17 Thread Yedidyah Bar David
Hi, 

(Replying also to the list) 

- Original Message -

 From: David Smith dsm...@mypchelp.com
 To: Yedidyah Bar David d...@redhat.com
 Sent: Monday, March 17, 2014 5:01:55 PM
 Subject: Re: [Users] Instructions to add a remote controlled power strip not
 in the native list?

 Hi Yedidyah,
 Keep in mind it appears that your instructions are assuming some level of in
 depth knowledge of *some* database not described in that thread.

 In other words, for someone not extremely familiar with the oVirt database
 location and tables, would not have a clue as to what you're talking about
 in this email.

 I'm guessing this database is located locally on my ovirt-engine, but I
 wouldn't know where to start in how to get into it without causing major
 problems (ie, do I need to turn off the engine first?) and it would help if
 there were a detailed example with sql commands to make the necessary
 modifications to the dB to add a fence agent completely.

This wasn't my email, it was Eli Mesika's. I just remembered that he sent it so 
it was easy to find. 

I agree that the instructions are not complete. 

The database was created during setup - you were asked about that and probably 
accepted the defaults, 
which create a local database called 'engine'. You can connect to it by doing: 
su - postgres 
psql engine 

Obviously, do not change anything before you understand what you are doing and 
have some good backup. 
You can read, and usually update, without taking the engine down. 

There is quite a lot of material on the ovirt wiki - please search and read a 
bit - e.g. for 'ovirt database'. 

Do not hesitate to ask (on-list) again if you have questions. 

You can also ask on irc for faster help. 

Best regards, 
-- 
Didi 
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] Instructions to add a remote controlled power strip not in the native list?

2014-03-17 Thread David Smith
Hi again Didi,

Thanks for your help, I'll do some digging.

Also, the below line made me chuckle.
Last time I was on IRC, there were crickets for an entire 8 hour day, not a
single response, just a lot of signin/off. ;)

Dave


On Mon, Mar 17, 2014 at 8:53 AM, Yedidyah Bar David d...@redhat.com wrote:



 You can also ask on irc for faster help.

 Best regards,
 --
 Didi


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


Re: [Users] Instructions to add a remote controlled power strip not in the native list?

2014-03-17 Thread Eli Mesika


- Original Message -
 From: Yedidyah Bar David d...@redhat.com
 To: David Smith dsm...@mypchelp.com
 Cc: Marek Grac mg...@redhat.com, users@ovirt.org, Eli Mesika 
 emes...@redhat.com
 Sent: Sunday, March 16, 2014 9:15:26 AM
 Subject: Re: [Users] Instructions to add a remote controlled power strip not 
 in the native list?
 
  From: David Smith dsm...@mypchelp.com
  To: Marek Grac mg...@redhat.com
  Cc: users@ovirt.org
  Sent: Friday, March 14, 2014 7:21:48 PM
  Subject: Re: [Users] Instructions to add a remote controlled power strip
  not
  in the native list?
 
  Hi Marek,
 
  that link requires a redhat login..
 
 Here:
 http://lists.ovirt.org/pipermail/users/2014-January/019655.html
 
 (Exactly one month ago I sent this link replying to the same question.
 Perhaps better to put this info on the wiki).

Sorry for jumping late in the game (was in PTO)
I had put the information in the following wiki
http://www.ovirt.org/Custom_Fencing

Please feel free to contact me directly on any issue 
Tahnks



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


Re: [Users] Instructions to add a remote controlled power strip not in the native list?

2014-03-16 Thread Yedidyah Bar David
 From: David Smith dsm...@mypchelp.com
 To: Marek Grac mg...@redhat.com
 Cc: users@ovirt.org
 Sent: Friday, March 14, 2014 7:21:48 PM
 Subject: Re: [Users] Instructions to add a remote controlled power strip not
 in the native list?

 Hi Marek,

 that link requires a redhat login..

Here: 
http://lists.ovirt.org/pipermail/users/2014-January/019655.html 

(Exactly one month ago I sent this link replying to the same question. 
Perhaps better to put this info on the wiki). 
-- 
Didi 
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] Instructions to add a remote controlled power strip not in the native list?

2014-03-14 Thread Itamar Heim

On 03/13/2014 07:03 PM, David Smith wrote:

hey can someone provide these mysterious instructions or at least point
me towards the direction of where this magical list of supported
fence-agents units is so I can try to figure it out myself?



that would be eli, already asked for in my previous reply.
until he replies, you can look at the vdc_options table at these values 
(they are not available out of the box via the config utility, as they 
would be overridden at upgrade):


VdsFenceType

upgrade/pre_upgrade/_config.sql:select 
fn_db_update_config_value('VdsFenceType','apc,apc_snmp,bladecenter,cisco_ucs,drac5,drac7,eps,hpblade,ilo,ilo2,ilo3,ilo4,ipmilan,rsa,rsb,wti','3.4');



VdsFenceOptionMapping

upgrade/pre_upgrade/_config.sql:select 
fn_db_update_config_value('VdsFenceOptionMapping','apc:secure=secure,port=ipport,slot=port;apc_snmp:port=port;bladecenter:secure=secure,port=ipport,slot=port;cisco_ucs:secure=ssl,slot=port;drac5:secure=secure,slot=port;drac7:;eps:slot=port;hpblade:port=port;ilo:secure=ssl,port=ipport;ipmilan:;ilo2:secure=ssl,port=ipport;ilo3:;ilo4:;rsa:secure=secure,port=ipport;rsb:;wti:secure=secure,port=ipport,slot=port','3.4');


VdsFenceOptionTypes
upgrade/pre_upgrade/_config.sql:select 
fn_db_add_config_value('VdsFenceOptionTypes','secure=bool,port=int,slot=int','general');








On Wed, Mar 12, 2014 at 12:18 AM, Itamar Heim ih...@redhat.com
mailto:ih...@redhat.com wrote:

On 03/11/2014 11:43 PM, David Smith wrote:

I modified, tested, and added via git (also submitted note in
rhbz#519731) support for at least basic power on/off of the raritan
devices I have (model DPXS12-20)
Now that I have a working fence agent for myself, is it possible
to tell
me how I can make the config change on my engine to add the
support for
the fence agent I created?


yes, you can change the config of the engine to add it - eli can
give more details (hopefully to be wikified later).
one caveat is i don't think we accommodated yet for customizing it,
so it may be overridden when you upgrade the engine.
(Eli, maybe consider changing to osinfo.d/ like format allowing both
our own config and user configs side by side)
to add this by default to engine, we'd need this to be in a released
version of fence-agents.


Thanks.


On Mon, Feb 17, 2014 at 5:43 AM, Itamar Heim ih...@redhat.com
mailto:ih...@redhat.com
mailto:ih...@redhat.com mailto:ih...@redhat.com wrote:

 On 02/17/2014 03:31 PM, Marek Grac wrote:

 On 02/17/2014 09:45 AM, Eli Mesika wrote:


 - Original Message -

 From: Yedidyah Bar David d...@redhat.com
mailto:d...@redhat.com
 mailto:d...@redhat.com mailto:d...@redhat.com
 To: Itamar Heim ih...@redhat.com
mailto:ih...@redhat.com
 mailto:ih...@redhat.com
mailto:ih...@redhat.com
 Cc: users@ovirt.org mailto:users@ovirt.org
mailto:users@ovirt.org mailto:users@ovirt.org

 Sent: Sunday, February 16, 2014 2:58:35 PM
 Subject: Re: [Users] Instructions to add a remote
 controlled power
 strip not in the native list?

 - Original Message -

 From: Itamar Heim ih...@redhat.com
mailto:ih...@redhat.com
 mailto:ih...@redhat.com
mailto:ih...@redhat.com
 To: David Smith dsm...@mypchelp.com
mailto:dsm...@mypchelp.com
 mailto:dsm...@mypchelp.com
mailto:dsm...@mypchelp.com, users@ovirt.org
mailto:users@ovirt.org
 mailto:users@ovirt.org
mailto:users@ovirt.org

 Sent: Saturday, February 15, 2014 2:57:00 AM
 Subject: Re: [Users] Instructions to add a
remote
 controlled power
 strip
 not in the native list?

 On 02/14/2014 07:37 PM, David Smith wrote:

 We use Raritan / Dominion PX remote power
 blocks, is there a way to
 easily add support for these?

 CCing Marek on that in case that he had something
to add
 from the
 fence-agents view since it may be already supported
 implicitly (like
 drac7 that is using actually ipmilan)


 No, Raritan are not supported yet (rhbz#519731)


 so david, if you can try to push the raritan support to
 fence-agents, 

Re: [Users] Instructions to add a remote controlled power strip not in the native list?

2014-03-14 Thread Marek Grac

On 03/14/2014 10:39 AM, Itamar Heim wrote:

On 03/13/2014 07:03 PM, David Smith wrote:

hey can someone provide these mysterious instructions or at least point
me towards the direction of where this magical list of supported
fence-agents units is so I can try to figure it out myself?




Perhaps you are looking for this:

https://access.redhat.com/site/articles/28601

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


Re: [Users] Instructions to add a remote controlled power strip not in the native list?

2014-03-14 Thread David Smith
Hi Marek,

that link requires a redhat login..


On Fri, Mar 14, 2014 at 2:56 AM, Marek Grac mg...@redhat.com wrote:

 On 03/14/2014 10:39 AM, Itamar Heim wrote:

 On 03/13/2014 07:03 PM, David Smith wrote:

 hey can someone provide these mysterious instructions or at least point
 me towards the direction of where this magical list of supported
 fence-agents units is so I can try to figure it out myself?


  Perhaps you are looking for this:

 https://access.redhat.com/site/articles/28601

 m,

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


Re: [Users] Instructions to add a remote controlled power strip not in the native list?

2014-03-14 Thread David Smith
i assumme this is in a database somewhere, you're making assumptions of my
knowledge span of ovirt and the location of these things.

thanks for the help anyway, i'm looking forward to getting this working,
hopefully there's a little more step by step insight somewhere from eli.


On Fri, Mar 14, 2014 at 2:39 AM, Itamar Heim ih...@redhat.com wrote:

 On 03/13/2014 07:03 PM, David Smith wrote:

 hey can someone provide these mysterious instructions or at least point
 me towards the direction of where this magical list of supported
 fence-agents units is so I can try to figure it out myself?


 that would be eli, already asked for in my previous reply.
 until he replies, you can look at the vdc_options table at these values
 (they are not available out of the box via the config utility, as they
 would be overridden at upgrade):

 VdsFenceType

 upgrade/pre_upgrade/_config.sql:select fn_db_update_config_value('
 VdsFenceType','apc,apc_snmp,bladecenter,cisco_ucs,drac5,
 drac7,eps,hpblade,ilo,ilo2,ilo3,ilo4,ipmilan,rsa,rsb,wti','3.4');


 VdsFenceOptionMapping

 upgrade/pre_upgrade/_config.sql:select fn_db_update_config_value('
 VdsFenceOptionMapping','apc:secure=secure,port=ipport,
 slot=port;apc_snmp:port=port;bladecenter:secure=secure,
 port=ipport,slot=port;cisco_ucs:secure=ssl,slot=port;
 drac5:secure=secure,slot=port;drac7:;eps:slot=port;hpblade:
 port=port;ilo:secure=ssl,port=ipport;ipmilan:;ilo2:secure=
 ssl,port=ipport;ilo3:;ilo4:;rsa:secure=secure,port=ipport;
 rsb:;wti:secure=secure,port=ipport,slot=port','3.4');

 VdsFenceOptionTypes
 upgrade/pre_upgrade/_config.sql:select fn_db_add_config_value('
 VdsFenceOptionTypes','secure=bool,port=int,slot=int','general');






 On Wed, Mar 12, 2014 at 12:18 AM, Itamar Heim ih...@redhat.com
 mailto:ih...@redhat.com wrote:

 On 03/11/2014 11:43 PM, David Smith wrote:

 I modified, tested, and added via git (also submitted note in
 rhbz#519731) support for at least basic power on/off of the
 raritan
 devices I have (model DPXS12-20)
 Now that I have a working fence agent for myself, is it possible
 to tell
 me how I can make the config change on my engine to add the
 support for
 the fence agent I created?


 yes, you can change the config of the engine to add it - eli can
 give more details (hopefully to be wikified later).
 one caveat is i don't think we accommodated yet for customizing it,
 so it may be overridden when you upgrade the engine.
 (Eli, maybe consider changing to osinfo.d/ like format allowing both
 our own config and user configs side by side)
 to add this by default to engine, we'd need this to be in a released
 version of fence-agents.


 Thanks.


 On Mon, Feb 17, 2014 at 5:43 AM, Itamar Heim ih...@redhat.com
 mailto:ih...@redhat.com
 mailto:ih...@redhat.com mailto:ih...@redhat.com wrote:

  On 02/17/2014 03:31 PM, Marek Grac wrote:

  On 02/17/2014 09:45 AM, Eli Mesika wrote:


  - Original Message -

  From: Yedidyah Bar David d...@redhat.com
 mailto:d...@redhat.com
  mailto:d...@redhat.com mailto:d...@redhat.com
 

  To: Itamar Heim ih...@redhat.com
 mailto:ih...@redhat.com
  mailto:ih...@redhat.com

 mailto:ih...@redhat.com
  Cc: users@ovirt.org mailto:users@ovirt.org
 mailto:users@ovirt.org mailto:users@ovirt.org


  Sent: Sunday, February 16, 2014 2:58:35 PM
  Subject: Re: [Users] Instructions to add a remote
  controlled power
  strip not in the native list?

  - Original Message -

  From: Itamar Heim ih...@redhat.com
 mailto:ih...@redhat.com
  mailto:ih...@redhat.com

 mailto:ih...@redhat.com
  To: David Smith dsm...@mypchelp.com
 mailto:dsm...@mypchelp.com
  mailto:dsm...@mypchelp.com

 mailto:dsm...@mypchelp.com, users@ovirt.org
 mailto:users@ovirt.org
  mailto:users@ovirt.org

 mailto:users@ovirt.org

  Sent: Saturday, February 15, 2014 2:57:00 AM
  Subject: Re: [Users] Instructions to add a
 remote
  controlled power
  strip
  not in the native list?

  On 02/14/2014 07:37 PM, David Smith wrote:

  We use Raritan / Dominion PX remote power
  blocks, is there a way to
  easily add support for these?

   

Re: [Users] Instructions to add a remote controlled power strip not in the native list?

2014-03-13 Thread David Smith
hey can someone provide these mysterious instructions or at least point me
towards the direction of where this magical list of supported fence-agents
units is so I can try to figure it out myself?




On Wed, Mar 12, 2014 at 12:18 AM, Itamar Heim ih...@redhat.com wrote:

 On 03/11/2014 11:43 PM, David Smith wrote:

 I modified, tested, and added via git (also submitted note in
 rhbz#519731) support for at least basic power on/off of the raritan
 devices I have (model DPXS12-20)
 Now that I have a working fence agent for myself, is it possible to tell
 me how I can make the config change on my engine to add the support for
 the fence agent I created?


 yes, you can change the config of the engine to add it - eli can give more
 details (hopefully to be wikified later).
 one caveat is i don't think we accommodated yet for customizing it, so it
 may be overridden when you upgrade the engine.
 (Eli, maybe consider changing to osinfo.d/ like format allowing both our
 own config and user configs side by side)
 to add this by default to engine, we'd need this to be in a released
 version of fence-agents.


 Thanks.


 On Mon, Feb 17, 2014 at 5:43 AM, Itamar Heim ih...@redhat.com
 mailto:ih...@redhat.com wrote:

 On 02/17/2014 03:31 PM, Marek Grac wrote:

 On 02/17/2014 09:45 AM, Eli Mesika wrote:


 - Original Message -

 From: Yedidyah Bar David d...@redhat.com
 mailto:d...@redhat.com
 To: Itamar Heim ih...@redhat.com
 mailto:ih...@redhat.com
 Cc: users@ovirt.org mailto:users@ovirt.org

 Sent: Sunday, February 16, 2014 2:58:35 PM
 Subject: Re: [Users] Instructions to add a remote
 controlled power
 strip not in the native list?

 - Original Message -

 From: Itamar Heim ih...@redhat.com
 mailto:ih...@redhat.com
 To: David Smith dsm...@mypchelp.com
 mailto:dsm...@mypchelp.com, users@ovirt.org
 mailto:users@ovirt.org

 Sent: Saturday, February 15, 2014 2:57:00 AM
 Subject: Re: [Users] Instructions to add a remote
 controlled power
 strip
 not in the native list?

 On 02/14/2014 07:37 PM, David Smith wrote:

 We use Raritan / Dominion PX remote power
 blocks, is there a way to
 easily add support for these?

 CCing Marek on that in case that he had something to add
 from the
 fence-agents view since it may be already supported
 implicitly (like
 drac7 that is using actually ipmilan)


 No, Raritan are not supported yet (rhbz#519731)


 so david, if you can try to push the raritan support to
 fence-agents, the ovirt side is usually just a config change.




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


Re: [Users] Instructions to add a remote controlled power strip not in the native list?

2014-03-12 Thread Itamar Heim

On 03/11/2014 11:43 PM, David Smith wrote:

I modified, tested, and added via git (also submitted note in
rhbz#519731) support for at least basic power on/off of the raritan
devices I have (model DPXS12-20)
Now that I have a working fence agent for myself, is it possible to tell
me how I can make the config change on my engine to add the support for
the fence agent I created?


yes, you can change the config of the engine to add it - eli can give 
more details (hopefully to be wikified later).
one caveat is i don't think we accommodated yet for customizing it, so 
it may be overridden when you upgrade the engine.
(Eli, maybe consider changing to osinfo.d/ like format allowing both our 
own config and user configs side by side)
to add this by default to engine, we'd need this to be in a released 
version of fence-agents.




Thanks.


On Mon, Feb 17, 2014 at 5:43 AM, Itamar Heim ih...@redhat.com
mailto:ih...@redhat.com wrote:

On 02/17/2014 03:31 PM, Marek Grac wrote:

On 02/17/2014 09:45 AM, Eli Mesika wrote:


- Original Message -

From: Yedidyah Bar David d...@redhat.com
mailto:d...@redhat.com
To: Itamar Heim ih...@redhat.com
mailto:ih...@redhat.com
Cc: users@ovirt.org mailto:users@ovirt.org
Sent: Sunday, February 16, 2014 2:58:35 PM
Subject: Re: [Users] Instructions to add a remote
controlled power
strip not in the native list?

- Original Message -

From: Itamar Heim ih...@redhat.com
mailto:ih...@redhat.com
To: David Smith dsm...@mypchelp.com
mailto:dsm...@mypchelp.com, users@ovirt.org
mailto:users@ovirt.org
Sent: Saturday, February 15, 2014 2:57:00 AM
Subject: Re: [Users] Instructions to add a remote
controlled power
strip
not in the native list?

On 02/14/2014 07:37 PM, David Smith wrote:

We use Raritan / Dominion PX remote power
blocks, is there a way to
easily add support for these?

CCing Marek on that in case that he had something to add
from the
fence-agents view since it may be already supported
implicitly (like
drac7 that is using actually ipmilan)


No, Raritan are not supported yet (rhbz#519731)


so david, if you can try to push the raritan support to
fence-agents, the ovirt side is usually just a config change.




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


Re: [Users] Instructions to add a remote controlled power strip not in the native list?

2014-03-11 Thread David Smith
I modified, tested, and added via git (also submitted note in rhbz#519731)
support for at least basic power on/off of the raritan devices I have
(model DPXS12-20)
Now that I have a working fence agent for myself, is it possible to tell me
how I can make the config change on my engine to add the support for the
fence agent I created?

Thanks.


On Mon, Feb 17, 2014 at 5:43 AM, Itamar Heim ih...@redhat.com wrote:

 On 02/17/2014 03:31 PM, Marek Grac wrote:

 On 02/17/2014 09:45 AM, Eli Mesika wrote:


 - Original Message -

 From: Yedidyah Bar David d...@redhat.com
 To: Itamar Heim ih...@redhat.com
 Cc: users@ovirt.org
 Sent: Sunday, February 16, 2014 2:58:35 PM
 Subject: Re: [Users] Instructions to add a remote controlled power
 strip not in the native list?

 - Original Message -

 From: Itamar Heim ih...@redhat.com
 To: David Smith dsm...@mypchelp.com, users@ovirt.org
 Sent: Saturday, February 15, 2014 2:57:00 AM
 Subject: Re: [Users] Instructions to add a remote controlled power
 strip
 not in the native list?

 On 02/14/2014 07:37 PM, David Smith wrote:

 We use Raritan / Dominion PX remote power blocks, is there a way to
 easily add support for these?

 CCing Marek on that in case that he had something to add from the
 fence-agents view since it may be already supported implicitly (like
 drac7 that is using actually ipmilan)


 No, Raritan are not supported yet (rhbz#519731)


 so david, if you can try to push the raritan support to fence-agents, the
 ovirt side is usually just a config change.

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


Re: [Users] Instructions to add a remote controlled power strip not in the native list?

2014-02-17 Thread Eli Mesika


- Original Message -
 From: Yedidyah Bar David d...@redhat.com
 To: Itamar Heim ih...@redhat.com
 Cc: users@ovirt.org
 Sent: Sunday, February 16, 2014 2:58:35 PM
 Subject: Re: [Users] Instructions to add a remote controlled power strip not 
 in the native list?
 
 - Original Message -
  From: Itamar Heim ih...@redhat.com
  To: David Smith dsm...@mypchelp.com, users@ovirt.org
  Sent: Saturday, February 15, 2014 2:57:00 AM
  Subject: Re: [Users] Instructions to add a remote controlled power strip
  not in the native list?
  
  On 02/14/2014 07:37 PM, David Smith wrote:
   We use Raritan / Dominion PX remote power blocks, is there a way to
   easily add support for these?

CCing Marek on that in case that he had something to add from the fence-agents 
view since it may be already supported implicitly (like drac7 that is using 
actually ipmilan)

  
   On a feature request side, seems like adding support for generic
   wouldn't be too hard; just ask for what the login/password prompts look
   like, what the main prompt is, and the command sequence to turn on and
   off a port as well as logout.
  
  
  
  
   ___
   Users mailing list
   Users@ovirt.org
   http://lists.ovirt.org/mailman/listinfo/users
  
  
  we use the fence-agent library - does it support these?
 
 Also, Eli posted instructions on how to manually add an agent:
 http://lists.ovirt.org/pipermail/users/2014-January/019655.html
 --
 Didi
 ___
 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] Instructions to add a remote controlled power strip not in the native list?

2014-02-17 Thread Itamar Heim

On 02/17/2014 03:31 PM, Marek Grac wrote:

On 02/17/2014 09:45 AM, Eli Mesika wrote:


- Original Message -

From: Yedidyah Bar David d...@redhat.com
To: Itamar Heim ih...@redhat.com
Cc: users@ovirt.org
Sent: Sunday, February 16, 2014 2:58:35 PM
Subject: Re: [Users] Instructions to add a remote controlled power
strip not in the native list?

- Original Message -

From: Itamar Heim ih...@redhat.com
To: David Smith dsm...@mypchelp.com, users@ovirt.org
Sent: Saturday, February 15, 2014 2:57:00 AM
Subject: Re: [Users] Instructions to add a remote controlled power
strip
not in the native list?

On 02/14/2014 07:37 PM, David Smith wrote:

We use Raritan / Dominion PX remote power blocks, is there a way to
easily add support for these?

CCing Marek on that in case that he had something to add from the
fence-agents view since it may be already supported implicitly (like
drac7 that is using actually ipmilan)


No, Raritan are not supported yet (rhbz#519731)


so david, if you can try to push the raritan support to fence-agents, 
the ovirt side is usually just a config change.

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


Re: [Users] Instructions to add a remote controlled power strip not in the native list?

2014-02-16 Thread Yedidyah Bar David
- Original Message -
 From: Itamar Heim ih...@redhat.com
 To: David Smith dsm...@mypchelp.com, users@ovirt.org
 Sent: Saturday, February 15, 2014 2:57:00 AM
 Subject: Re: [Users] Instructions to add a remote controlled power strip not 
 in the native list?
 
 On 02/14/2014 07:37 PM, David Smith wrote:
  We use Raritan / Dominion PX remote power blocks, is there a way to
  easily add support for these?
 
  On a feature request side, seems like adding support for generic
  wouldn't be too hard; just ask for what the login/password prompts look
  like, what the main prompt is, and the command sequence to turn on and
  off a port as well as logout.
 
 
 
 
  ___
  Users mailing list
  Users@ovirt.org
  http://lists.ovirt.org/mailman/listinfo/users
 
 
 we use the fence-agent library - does it support these?

Also, Eli posted instructions on how to manually add an agent:
http://lists.ovirt.org/pipermail/users/2014-January/019655.html
-- 
Didi
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] Instructions to add a remote controlled power strip not in the native list?

2014-02-14 Thread Itamar Heim

On 02/14/2014 07:37 PM, David Smith wrote:

We use Raritan / Dominion PX remote power blocks, is there a way to
easily add support for these?

On a feature request side, seems like adding support for generic
wouldn't be too hard; just ask for what the login/password prompts look
like, what the main prompt is, and the command sequence to turn on and
off a port as well as logout.




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



we use the fence-agent library - does it support these?
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users