19f3e7a325
With this commit we are able to generate the fencing configuration for IPMI hosts before deployment, and thus use it as part of the initial deployment run. The reason we can generate it before hand is the following: puppet::tripleo is capable of matching its own host via https://github.com/openstack/puppet-tripleo/blob/master/manifests/fencing.pp#L73 and by doing that each node will create its own stonith device. It does so by looking at the macaddress<->IPMI table and if it detects it's own macaddress it will create the IPMI stonith device for its own hostname. Concurrent stonith resource creation from different nodes is possible in puppet-pacemaker since change I8be5d5d1a9894b0e2915459b10ea2feed703ba8e got merged. Tested as follows on a virtual vbmc environment: 1. Before deployment: $ openstack overcloud generate fencing instackenv.json --output fence.yaml 2. Deployed overcloud adding "fence.yaml" 3. Verified stonith configuration: [root@controller-0 ~]# pcs status |grep stonith stonith-fence_ipmilan-525400c36fc9 (stonith:fence_ipmilan): Started controller-0 stonith-fence_ipmilan-5254005c160d (stonith:fence_ipmilan): Started controller-2 stonith-fence_ipmilan-525400ed3293 (stonith:fence_ipmilan): Started controller-1 [root@controller-0 ~]# pcs property |grep stonith stonith-enabled: true 4. Verified the fencing of a specific node: [root@controller-0 ~]# pcs stonith fence controller-1 Node: controller-1 fenced <indeed controller-1 has been fenced> Same test run on BM: 1. Before deployment: $ openstack overcloud generate fencing instackenv.json --output fence.yaml 2. Deployed overcloud adding "fence.yaml" 3. Verified stonith configuration: [root@controller-0 ~]# pcs status |grep stonith stonith-fence_ipmilan-1866da6126a0 (stonith:fence_ipmilan): Started overcloud-controller-0 stonith-fence_ipmilan-1866da612109 (stonith:fence_ipmilan): Started overcloud-controller-1 stonith-fence_ipmilan-1866da5faed8 (stonith:fence_ipmilan): Started overcloud-controller-2 stonith-fence_ipmilan-1866da612373 (stonith:fence_ipmilan): Started overcloud-controller-2 stonith-fence_ipmilan-1866da612295 (stonith:fence_ipmilan): Started overcloud-controller-0 [root@overcloud-controller-0 ~]# pcs property |grep stonith stonith-enabled: true 4. Verified the fencing of a specific node: [root@overcloud-controller-0 ~]# pcs stonith fence overcloud-controller-1 & ping overcloud-controller-1 [1] 168504 PING overcloud-controller-1.localdomain (172.17.0.14) 56(84) bytes of data. 64 bytes from overcloud-controller-1.localdomain (172.17.0.14): icmp_seq=1 ttl=64 time=0.139 ms 64 bytes from overcloud-controller-1.localdomain (172.17.0.14): icmp_seq=2 ttl=64 time=0.135 ms 64 bytes from overcloud-controller-1.localdomain (172.17.0.14): icmp_seq=3 ttl=64 time=0.132 ms 64 bytes from overcloud-controller-1.localdomain (172.17.0.14): icmp_seq=4 ttl=64 time=0.150 ms 64 bytes from overcloud-controller-1.localdomain (172.17.0.14): icmp_seq=5 ttl=64 time=0.161 ms <timeout> Closes-Bug: #1765727 Change-Id: I41f81dc9d68bcf23e6171e35bb053a3943f50c01 |
||
|---|---|---|
| .. | ||
| __init__.py | ||
| config.py | ||
| glance.py | ||
| keystone.py | ||
| nodes.py | ||
| overcloudrc.py | ||
| parameters.py | ||
| passwords.py | ||
| plan.py | ||
| roles.py | ||
| swift.py | ||
| tarball.py | ||
| time_functions.py | ||
| validations.py | ||