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

[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 <emesika at redhat.com> wrote:

>
>
> ----- Original Message -----
> > From: "David Smith" <dsmith at mypchelp.com>
> > To: "Eli Mesika" <emesika at redhat.com>
> > Cc: "Marek Grac" <mgrac at redhat.com>, "users" <users at ovirt.org>,
> "Yedidyah Bar David" <didi at 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 <emesika at redhat.com> wrote:
> >
> > >
> > >
> > > ----- Original Message -----
> > > > From: "David Smith" <dsmith at mypchelp.com>
> > > > To: "Eli Mesika" <emesika at redhat.com>
> > > > Cc: "Marek Grac" <mgrac at redhat.com>, "users" <users at ovirt.org>,
> > > "Yedidyah Bar David" <didi at 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
> > > >
> > >
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20140325/de5e0f24/attachment-0001.html>