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
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;