dc0b057f6e
Currently container based CI jobs are implementing their own logic to transform overcloud_containers.yaml to a file that reflects the container images and registry required to run their job [1] unless the job requires the exact images which the static overcloud_containers.yaml provides[2]. This change adds a template overcloud_containers.yaml.j2 which will exist in parallel to overcloud_containers.yaml until all downstream users of overcloud_containers.yaml switch to a templated approach. This change is the first step to write commands which allow overcloud_containers.yaml to be built for a specific enviroment, including version based tags and reducing the image list to those needed by the deployment. The test test_container_images_yaml_in_sync will ensure that any changes made to overcloud_containers.yaml won't pass until they're made to overcloud_containers.yaml.j2 as well. This will keep them in sync until overcloud_containers.yaml is removed. [1] https://github.com/rdo-infra/ansible-role-rdo-kolla-build/blob/master/tasks/main.yml#L39-L75 [2] https://github.com/openstack/tripleo-quickstart-extras/blob/master/roles/overcloud-prep-containers/templates/overcloud-prep-containers.sh.j2#L18 Change-Id: I4fe18565362f9f308dd9957aeb9bc0f7498590a6 Partial-Bug: #1696598
Team and repository tags
tripleo-common
A common library for TripleO workflows.
- Free software: Apache license
- Documentation: http://docs.openstack.org/developer/tripleo-common
- 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