<div dir="ltr">All right, serious progress. Thanks to all for your nudges in the right direction.<div>I've managed to get my ovirt to recognize and use the agent.</div><div>I have a new problem however</div><div><br></div>
<div>I get this message when the fence_raritan agent is run: Ignoring unknown option 'option=status' fence</div><div>So it appears that my fence_raritan agent is being sent "--option" instead of "--action"</div>
<div><br></div><div>Since the default behavior is "reboot" (fence_raritan expects --action= not --option=) the systems reboot every time a status request is sent :( hehe</div><div><br></div><div>Related:? <a href="https://bugzilla.redhat.com/show_bug.cgi?id=987446">https://bugzilla.redhat.com/show_bug.cgi?id=987446</a></div>
<div>I'm not using "concurrent"</div><div><br></div><div>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.</div><div>
Is this problem within a fencing package, ovirt, or other?</div><div><br></div><div>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?</div>
<div><br></div><div><br></div><div>This is what I've changed for now, using 3.3 cluster;</div><div><div>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;</div>
</div><div><br></div><div>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;<br></div></div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Mon, Mar 24, 2014 at 2:07 PM, Eli Mesika <span dir="ltr"><<a href="mailto:emesika@redhat.com" target="_blank">emesika@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class=""><br>
<br>
----- Original Message -----<br>
> From: "David Smith" <<a href="mailto:dsmith@mypchelp.com">dsmith@mypchelp.com</a>><br>
> To: "Eli Mesika" <<a href="mailto:emesika@redhat.com">emesika@redhat.com</a>><br>
</div><div class="">> Cc: "Marek Grac" <<a href="mailto:mgrac@redhat.com">mgrac@redhat.com</a>>, "users" <<a href="mailto:users@ovirt.org">users@ovirt.org</a>>, "Yedidyah Bar David" <<a href="mailto:didi@redhat.com">didi@redhat.com</a>><br>
> Sent: Friday, March 21, 2014 4:33:17 PM<br>
> Subject: Re: [Users] Instructions to add a remote controlled power strip not in the native list?<br>
><br>
</div><div class="">> Hey guys,<br>
><br>
> I submitted an initial agent for raritan to the fence-agents group, however<br>
> I have a feeling after experimenting with the ipmilan agent that my agent<br>
> won't work with oVirt;<br>
<br>
</div>Can you please elaborate on that ? what will not work and why this is related to the ipmilan card ?<br>
<div class=""><br>
><br>
> Is the command set for each agent determined by the oVirt database itself,<br>
> in other words, when I add the agent the abilities are then added?<br>
<br>
</div>Please see <a href="http://www.ovirt.org/Custom_Fencing" target="_blank">http://www.ovirt.org/Custom_Fencing</a> for the exact set of fields in database involved in that.<br>
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<br>
<div class=""><br>
><br>
> For example the agent I submitted only has support for connectivity<br>
> settings and power on/off/reboot as well as some delays. Also currently it<br>
> requires that the port be specified as a path ie /system1/outlet1<br>
><br>
> Will this work as an outlet path?<br>
<br>
</div>You can try to put that in the options field in the UI for the PM agent definition , i.e "port=/system1/outlet1"<br>
<div class=""><br>
> Minimum commands required to work?<br>
<br>
</div>Not sure I go you here , please elaborate/explain<br>
<br>
><br>
> Thanks<br>
><br>
</blockquote></div><br></div>