<commit_before>---
title: Custom Fencing
authors: emesika
wiki_title: Custom Fencing
wiki_revision_count: 11
wiki_last_updated: 2015-03-18
---

# Custom Fencing

Here are detailed instructions how to add a custom agent:

## Pre oVirt 3.5 releases

a) Add your new agent to VdsFenceType option_value in vdc_options table for the relevant cluster version
b) Add agent options mappings to VdsFenceOptionMapping option_value in vdc_options table for the relevant cluster version
c) If the agent maps actually to another agent , add that to FenceAgentMapping option_value in vdc_options
 Example :

        Adding zzz agent support for version 3.3 that maps internally to ipmi and have just port setting (from: port, slot, secure) that maps to the fencing script ipport
        a) VdsFenceType for 3.3 becomes "apc,apc_snmp,bladecenter,cisco_ucs,drac5,eps,ilo,ilo2,ilo3,ilo4,ipmilan,rsa,rsb,wti,zzz"
         b) VdsFenceOptionMapping for 3.3 becomes "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;zzz:port=ipport"
         c) FenceAgentMapping becomes "ilo2=ilo,ilo3=ipmilan,ilo4=ipmilan,zzz=ipmilan"

NOTES

1) Please backup your database
2) You should restart the engine for this to take place
3) Custom definitions will be overridden in your next upgrade , for the long run please fill RFE so it will be part of the supported agents

## oVirt 3.5

In oVirt 3.5 we had added custom fence configuration keys :

        CustomFenceAgentMapping
        CustomFenceAgentDefaultParams
        CustomVdsFenceOptionMapping
        CustomVdsFenceType

Those keys are accessible from the engine-config util

Example : Adding zzz agent support for version 3.5 that maps internally to ipmi and have just port setting (from: port, slot, secure) that maps to the fencing script ipport

        engine-config -s CustomVdsFenceType=zzz
        engine-config -s CustomFenceAgentMapping=zzz=ipmilan
        engine-config -s CustomVdsFenceOptionMapping=zzz:port=ipport

In this case those changes remains valid after oVirt upgrades as well, so please use that me6thod from oVirt 3.5 and on.<commit_msg>oVirt 3.5<commit_after>---
title: Custom Fencing
authors: emesika
wiki_title: Custom Fencing
wiki_revision_count: 11
wiki_last_updated: 2015-03-18
---

# Custom Fencing

Here are detailed instructions how to add a custom agent:

## Pre oVirt 3.5 releases

a) Add your new agent to VdsFenceType option_value in vdc_options table for the relevant cluster version
b) Add agent options mappings to VdsFenceOptionMapping option_value in vdc_options table for the relevant cluster version
c) If the agent maps actually to another agent , add that to FenceAgentMapping option_value in vdc_options
 Example :

        Adding zzz agent support for version 3.3 that maps internally to ipmi and have just port setting (from: port, slot, secure) that maps to the fencing script ipport
        a) VdsFenceType for 3.3 becomes "apc,apc_snmp,bladecenter,cisco_ucs,drac5,eps,ilo,ilo2,ilo3,ilo4,ipmilan,rsa,rsb,wti,zzz"
         b) VdsFenceOptionMapping for 3.3 becomes "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;zzz:port=ipport"
         c) FenceAgentMapping becomes "ilo2=ilo,ilo3=ipmilan,ilo4=ipmilan,zzz=ipmilan"

NOTES

1) Please backup your database
2) You should restart the engine for this to take place
3) Custom definitions will be overridden in your next upgrade , for the long run please fill RFE so it will be part of the supported agents

## oVirt 3.5

In oVirt 3.5 we had added custom fence configuration keys :

        CustomFenceAgentMapping
        CustomFenceAgentDefaultParams
        CustomVdsFenceOptionMapping
        CustomVdsFenceType

Those keys are accessible from the engine-config util

Example : Adding zzz agent support for version 3.5 that maps internally to ipmi and have just port setting (from: port, slot, secure) that maps to the fencing script ipport

        engine-config -s CustomVdsFenceType="zzz"
        engine-config -s CustomFenceAgentMapping="zzz=ipmilan"
        engine-config -s CustomVdsFenceOptionMapping="zzz:port=ipport"

In this case those changes remains valid after oVirt upgrades as well, so please use that me6thod from oVirt 3.5 and on.
{'fraction_non_alphanumeric': 0.06814345991561181, 'fraction_numerical': 0.017721518987341773, 'mean_word_length': 5.101673101673102, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '5703982', 'n_tokens_mistral': 1691, 'n_tokens_neox': 1633, 'n_words': 500}