381fc8c4fe
Presently, "openstack overcloud config download" only supports the OS::HeatSoftwareDeploymentGroup (plural) resources from deploy-steps.yaml. This patch adds support to the command to also pull the deployment resources for each individual server from the OS::Heat::Value resources called "TripleODeployment", as well as other SoftwareDeploymentGroup resources not from deploy-steps.j2. See the Depends-On tripleo-heat-templates patch for how these resources are mapped. These deployments are applied by additional plays in the generated playbooks. Instead of having to reimplement each deployment in a native group:ansible, the ansible tasks just trigger the deployments by calling 55-heat-config remotely with the rendered json deployment data for whatever deployment is being applied. This method saves us from having to migrate all these resources to native ansible (and requring all end users to do so). Also included is a helper script called tripleo-config-download to run the config download outside of Mistral. implements: blueprint ansible-config-download Change-Id: I7d7f6b831b8566390d8f747fb6f45e879b0392ba Depends-On: Ic2af634403b1ab2924c383035f770453f39a2cd5
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: http://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 tripleoValidations
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 validationsFinally 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_keyRunning 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.jsonRunning 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