Documentation Assessment: Two changes will be required for this item: 1. Remove manual fencing steps from director guide 2. Add auto fencing configuration to the advanced overcloud guide"
Assigning to Martin for review. Martin, can you work with Dan to determine an appropriate placement and structure for this content?
Researching requirements
in my opinion, it will be good to add to 14.3.2.1 an example on how the fencing.yml should look like.
*** Bug 1452246 has been marked as a duplicate of this bug. ***
this is how I built my instackenv file and the output from the fencing.yml: [stack@puma33 ~]$ cat instackenv.json { "nodes":[ { "name": "puma04", "pm_type":"pxe_ipmitool", "mac":[ "44:1e:a1:73:39:91" ], "cpu":"1", "memory":"4096", "disk":"40", "arch":"x86_64", "pm_user":"admin", "pm_password":"admin", "pm_addr":"10.35.160.18" }, [stack@puma33 ~]$ cat fencing.yml parameter_defaults: EnableFencing: true FencingConfig: devices: - agent: fence_ipmilan host_mac: 44:1e:a1:73:39:91 params: action: reboot ipaddr: 10.35.160.18 lanplus: true login: admin passwd: admin pcmk_host_list: puma04 privlvl: administrator
Added edits from peer review.
Guides have been updated: https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/11/html-single/advanced_overcloud_customization/#sect-Fencing_the_Controller_Nodes https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/11/html-single/director_installation_and_usage/