RETIRED, A Python library for code common to TripleO CLI and TripleO UI.
Go to file
Emilien Macchi 82bf5adc58 Implement tripleo-container-tag role
A new Ansible role to tag containers managed by Pacemaker.
This role will be consummed by services managed by Pacemaker.

Requirements
------------

It requires Docker or Podman on the host, depending which container CLI
is used.

Role variables
--------------

- container_image: -- Name of the container image to tag.
- container_image_latest: -- Name of the tag.
- container_cli: -- Name of the Container CLI tool (default to docker).

Example Playbook
----------------

Sample playbook to call the role:

  - name: Tag Pacemaker containers
    hosts: all
    roles:
      - tripleo-container-tag
    vars:
      container_image: haproxy
      container_image_latest: pcmklatest
      container_cli: docker

In THT, we'll consume this role for pacemaker-managed services, so we
can tag the images during the deployment, the updates and the upgrades
by using the same Ansible task.

Change-Id: I61039cdaa6798e8ae7c918f772d863dc1b67ae02
2018-11-05 19:45:22 +00:00
ansible_plugins/callback Ansible json error callback plugin 2018-05-31 07:46:10 -04:00
container-images Merge "Add crane service to overcloud_containers.yaml.j2" 2018-10-29 23:01:54 +00:00
contrib Rename contrib to container-images for packaging 2017-04-07 16:56:29 +12:00
doc/source Remove create_default_deployment_plan workflow 2018-06-26 10:04:57 +01:00
healthcheck Fix nova-api healthcheck in case of nova metadata wsgi 2018-10-12 11:57:56 +02: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 Merge "Increase size for security hardened images" 2018-10-19 18:55:36 +00:00
playbooks Fix skip of octavia-undercloud Ansible role 2018-10-08 09:09:27 +00:00
releasenotes Implement tripleo-container-tag role 2018-11-05 19:45:22 +00:00
roles Implement tripleo-container-tag role 2018-11-05 19:45:22 +00:00
scripts Add debug to container image prepare 2018-10-18 17:19:14 -06:00
tools Add bashate in gate jobs and fix existing errors 2018-09-17 11:36:57 +02:00
tripleo_common Use DockerRegistryMirror to proxy requests 2018-11-01 14:51:39 +13:00
undercloud_heat_plugins Add custom subclass to revert mapping 2018-03-27 12:33:24 +02:00
workbooks Merge "Change ceph-ansible fetch directory format on upgrade from Q to R" 2018-10-17 17:53:56 +00:00
zuul.d Remove non-voting scenarios from gate 2018-10-31 12:59:14 -06: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 Update README to pass RST strict test 2018-08-24 07:39:52 -04:00
babel.cfg Initial Cookiecutter Commit. 2015-04-29 13:34:49 +02:00
requirements.txt Revert "TLS by default for the overcloud" 2018-05-16 17:45:02 -04:00
setup.cfg Add wrapper for openshift-ansible docker command 2018-10-05 18:35:37 +02:00
setup.py Updated from global requirements 2017-03-10 03:40:32 +00:00
sudoers Add wrapper for openshift-ansible docker command 2018-10-05 18:35:37 +02:00
test-requirements.txt Replace skopeo inspect with python 2018-10-15 09:18:40 -04:00
tox.ini Add bashate in gate jobs and fix existing errors 2018-09-17 11:36:57 +02: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