This commit extends actions/parameters to generate
fencing parameters for nodes using staging-ovirt (fence_rhevm).
Given instackenv.json content like:
{
"nodes":[
{
"name":"ctrl01",
"pm_type":"staging-ovirt",
"mac": [
"56:6f:71:33:00:0d"
],
"arch": "x86_64",
"pm_user":"admin@internal",
"pm_password":"redhat",
"pm_addr":"10.0.0.141",
"pm_vm_name":"ctrl01"
}
...
Here the generated fence.yaml:
parameter_defaults:
EnableFencing: true
FencingConfig:
devices:
- agent: fence_rhevm
host_mac: 56:6f:71:33:00:0d
params:
ipaddr: 10.0.0.141
login: admin@internal
passwd: redhat
port: ctrl01
ssl: 1
ssl_insecure: 1
And the resulting pacemaker stonith resource:
stonith-fence_rhevm-566f7133000d (stonith:fence_rhevm:( Started overcloud-controller-1
To have this working 'out of the box' we assume the worst case
scenario of ovirt-engine using a self-signed certificate, so
we explicitly ssl_insecure=1.
Users/Operators should be aware of this and eventually adjust
the value accordingly.
NOTE: this is not a 100% clean cherry pick.
Change-Id: If14e0e0a87cacd857762c955288fd71d052d8bb4
(cherry picked from commit c13c9cf5a2)
2e3431e8a8