There are a number of situations in which it is desirable to add additional fence agents to the manager. For example, * Testing/demoing RHEV with nested KVM (fence-virsh) * Testing RHEV on a new hardware type Currently, adding a new agent requires modifying (at least) the VdsFenceType and VdsFenceOptionMapping configuration settings in the database, which is both ugly and risky. It would be useful to have a "supported" method for adding additional fence agents. "Supported" == we support the method of adding the agents, not that we support the additional agents themselves.
maybe what we did for custom properties is relevant here? we just added another config for user defined. here it would be CustomVdsFenceType, CustomVdsFenceOptionMapping and all code paths would be concatanating these with the builtin ones.
So did this get bumped off 3.3? Customer was after something like... vdsFenceType=script vdsFenceOptionMapping=/pathtoscripttoexecute/serialfence the serialfence script would then execute the reset We wouldn't provide the script per se, just the mechanism to align to an customer abstract script. The workaround is to see if we can do this by making direct changes into the database. The long term BZ is to provide an interface via RHEVM gui to allow users to add in a specified fencing mechnism, in this case an ad-hoc script path I'm going to be testing the "unsupported" workaround mentioned at the top this week but wanted to check on target release for this bz in rhev
So the customer would be ok with maintaining the scripts on each of the hosts. This would not be the ideal situation but, as I understand it, that would be the easiest way to provide the service without having to change the current RHEV fencing methodology.
Examples of how that worked prior to 3.5 in 3.5 can be found here: http://www.ovirt.org/Custom_Fencing comments to the tester --------------------------- 1) Have 2 Hosts A & B in the cluster, A with PM configured 2) lets say that A is using apc_snmp for example 3) Copy on B:/usr/sbin/fence_apc_snmp to /usr/sbin/fence_custom 4) Follow instructions on http://www.ovirt.org/Custom_Fencing#oVirt_3.5 to add "custom" as custom fencing agent 5) Restart engine 6) Edit host A and change it to use "custom" as fence agent 7) Click the TEST button and see that it works
Verified with ovirt-engine-3.5.0-0.0.master.20140821064931.gitb794d66.el6.noarch according to TCMS plan 14443.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2015-0158.html
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days