Bug 1452246

Description of problem:

Configuring fencing device on overcloud nodes using director is one of the major feature introduced in OSP11 But I don't much information on this topic in our official guides. 

Only release note [1] is having small text on this topic, command given here is wrong, it should be "openstack overcloud generate fencing instackenv"

~~~
BZ#1242422
Automatic fencing setup can be used in director for easier High Availability deployments and upgrades. To benefit from the new feature, use the 'overcloud generate fencing' command.
~~~

Issued the same command on my test setup: I am not sure about the usage of this like what should i provide in place of instackenv is this instackenv.json file or something else? It will be great if we can add example for this in our official guide. 

~~~
$ openstack overcloud generate fencing --help
usage: openstack overcloud generate fencing [-h] [-a FENCE_ACTION]
                                            [--delay DELAY] [--ipmi-lanplus]
                                            [--ipmi-cipher IPMI_CIPHER]
                                            [--ipmi-level IPMI_LEVEL]
                                            [--output OUTPUT]
                                            instackenv

Generate fencing parameters

positional arguments:
  instackenv

optional arguments:
  -h, --help            show this help message and exit
  -a FENCE_ACTION, --action FENCE_ACTION
                        Operation to perform. Valid operations: on, off,
                        reboot, status, list, diag, monitor or metadata. You
                        should generally not use this option.
  --delay DELAY         Wait DELAY seconds before fencing is started
  --ipmi-lanplus        Use Lanplus. Defaults to: false
  --ipmi-cipher IPMI_CIPHER
                        Ciphersuite to use (same as ipmitool -C parameter.
  --ipmi-level IPMI_LEVEL
                        Privilegel level on IPMI device. Valid levels:
                        callback, user, operator, administrator.
  --output OUTPUT       Write parameters to a file
~~~


[1] https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/11/html-single/release_notes/#new_tech_previews

Version-Release number of selected component (if applicable):
RHEL OSP 11

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info: