On master this command is currently broken: (undercloud) [stack@undercloud ~]$ openstack overcloud generate fencing instackenv.json --output fencing.yaml Invalid input [name=generate_fencing_parameters, class=DirectWorkflowSpec, missing=['os_auth', 'fence_action']] The reason for this is that via (A) I63f3a579af5aa70080f8c9cdd5eb0e8f5b3d17da (Add workflow to generate fencing parameters) we moved to use a workflow in order to generate fencing parameters. This workflow took a bunch of inputs which we then deprecated via two different ways: (B) os_auth https://review.openstack.org/#/c/570349/ and https://review.openstack.org/#/c/567896/ we removed some for pxe_ssh but we did not do it fully in the workbooks (C) fence_action Same goes for https://review.openstack.org/#/c/550028/ and https://review.openstack.org/#/c/556211/ we removed fence_action but since the workflow still used it as a parameter we broke things Problem is that the review at (A) got proposed before(B) and (C), but was merged after them. So it was never amended to account for the changes introduced in (B) and (C). This change amends things so that the command works correctly again: (undercloud) [stack@undercloud ~]$ openstack overcloud generate fencing instackenv.json --output fencing.yaml (undercloud) [stack@undercloud ~]$ ls -l fencing.yaml -rw-rw-r--. 1 stack stack 513 Jun 28 15:46 fencing.yaml Change-Id: I0262c493c217b64891e7da1bb3853b0d1366faef Closes-Bug: #1779168
Team and repository tags
tripleo-common
A common library for TripleO workflows.
- Free software: Apache license
- Documentation: https://docs.openstack.org/tripleo-common/latest/
- Source: http://git.openstack.org/cgit/openstack/tripleo-common
- Bugs: https://bugs.launchpad.net/tripleo-common
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