RETIRED, A Python library for code common to TripleO CLI and TripleO UI.
Go to file
Chris Jones 19f3e7a325 Allow fencing config generation before deployment.
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
2018-04-23 11:42:16 +02:00
container-images Merge "Activate another set of healthchecks" 2018-04-17 13:36:07 +00:00
contrib Rename contrib to container-images for packaging 2017-04-07 16:56:29 +12:00
doc/source Update the documentation link for doc migration 2017-07-25 15:00:27 +08:00
healthcheck Merge "Activate another set of healthchecks" 2018-04-17 13:36:07 +00:00
heat_docker_agent Remove /etc/os-net-config/config.json in os-apply-config 2018-03-22 18:44:00 -04:00
image-yaml Add openvswitch element back in 2018-03-21 15:07:43 -06:00
playbooks Merge "Fix parameter indentation on Swift rebalance playbook" 2018-04-03 05:30:29 +00:00
releasenotes config download support for a fixed directory 2018-04-17 17:15:17 -07:00
roles Use ansible_hostname 2018-03-07 13:55:23 -05:00
scripts Merge "Add file type check to upload-swift-artifacts" 2018-03-13 12:43:57 +00:00
tools Avoid tox_install.sh for constraints support 2017-12-02 22:47:24 +00:00
tripleo_common Allow fencing config generation before deployment. 2018-04-23 11:42:16 +02:00
undercloud_heat_plugins Add custom subclass to revert mapping 2018-03-27 12:33:24 +02:00
workbooks Merge "ffwd-upgrade cli - adds ffwd_upgrade_converge_plan task for noops" 2018-04-17 14:58:04 +00:00
zuul.d zuul: run ceph scenarios when touching actions/ansible.py 2018-04-03 10:25:18 -07:00
.coveragerc Make coverage tests work 2015-11-30 23:01:07 +00:00
.gitignore Add ansible playbook for configuring octavia 2018-01-10 14:37:01 +00:00
.gitreview Added .gitreview 2015-04-09 13:57:40 +00:00
.mailmap Initial Cookiecutter Commit. 2015-04-29 13:34:49 +02:00
.testr.conf Initial Cookiecutter Commit. 2015-04-29 13:34:49 +02:00
CONTRIBUTING.rst Update and replace http with https for doc links 2017-10-06 13:54:31 +00:00
HACKING.rst Update the documentation link for doc migration 2017-07-25 15:00:27 +08:00
LICENSE Initial Cookiecutter Commit. 2015-04-29 13:34:49 +02:00
README.rst Add docs for reloading workbooks during development 2018-01-04 13:25:31 +00:00
babel.cfg Initial Cookiecutter Commit. 2015-04-29 13:34:49 +02:00
requirements.txt Switch to concurrent.futures for container prepare/upload 2018-04-05 21:04:06 +00:00
setup.cfg Merge "Switch to concurrent.futures for container prepare/upload" 2018-04-10 20:36:28 +00:00
setup.py Updated from global requirements 2017-03-10 03:40:32 +00:00
sudoers Merge "Fix chown command for tripleo validation." 2018-02-19 20:46:07 +00:00
test-requirements.txt Updated from global requirements 2018-03-15 09:37:43 +00:00
tox.ini Avoid tox_install.sh for constraints support 2017-12-02 22:47:24 +00:00

README.rst

Team and repository tags

image

tripleo-common

A common library for TripleO workflows.

Action Development

When developing new actions, you will checkout a copy of tripleo-common to an undercloud machine and add actions as needed. To test the actions they need to be installed and selected services need to be restarted. Use the following code to accomplish these tasks. :

sudo rm -Rf /usr/lib/python2.7/site-packages/tripleo_common*
sudo python setup.py install
sudo cp /usr/share/tripleo-common/sudoers /etc/sudoers.d/tripleo-common
sudo systemctl restart openstack-mistral-executor
sudo systemctl restart openstack-mistral-engine
# this loads the actions via entrypoints
sudo mistral-db-manage populate
# make sure the new actions got loaded
mistral action-list | grep tripleo

Workflow Development ------------------

When developing new workflows, you will need to reload the modified workflows, e.g the following will reload all the workflows from the default packaged location, or you can use a similar approach to replace only a single workbook while under development. :

for workbook in $(openstack workbook list -f value -c Name | grep tripleo); do
    openstack workbook delete $workbook
done
for workflow in $(openstack workflow list -f value -c Name | grep tripleo); do
    openstack workflow delete $workflow
done
for workbook in $(ls /usr/share/openstack-tripleo-common/workbooks/*); do
    openstack workbook create $workbook
done

Validations

Prerequisites

If you haven't installed the undercloud with the enable_validations set to true, you will have to prepare your undercloud to run the validations:

$ sudo pip install git+https://git.openstack.org/openstack/tripleo-validations
$ sudo yum install ansible
$ sudo useradd validations

Finally you need to generate an SSH keypair for the validation user and copy it to the overcloud's authorized_keys files:

$ mistral execution-create tripleo.validations.v1.copy_ssh_key

Running validations using the mistral workflow

Create a context.json file containing the arguments passed to the workflow:

{
  "validation_names": ["512e", "rabbitmq-limits"]
}

Run the tripleo.validations.v1.run_validations workflow with mistral client:

mistral execution-create tripleo.validations.v1.run_validations context.json

Running groups of validations

Create a context.json file containing the arguments passed to the workflow:

{
  "group_names": ["network", "post-deployment"]
}

Run the tripleo.validations.v1.run_groups workflow with mistral client:

mistral execution-create tripleo.validations.v1.run_groups context.json