RETIRED, A Python library for code common to TripleO CLI and TripleO UI.
Go to file
James Slagle abafea837c Workflow and action for deployment failures
Adds a new workflow and corresponding custom action for querying the
ansible failures that occurred during a plan deployment with
config-download.

Relies on the json-error.py ansible callback plugin to provide a
structured data format for the errors.

Change-Id: I16d2dd0b3022cd5964919d07dd0ec603490a3ed7
(cherry picked from commit e8c521acf1)
2019-02-28 13:21:10 -05:00
ansible_plugins/callback Ansible json error callback plugin 2019-02-21 10:23:40 -05:00
container-images Cleanup old MariaDB cruft from override file 2019-02-13 14:05:36 -05: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 Stops growth of massive dentry cache growth 2019-02-19 21:43:10 -05:00
heat_docker_agent Remove /etc/os-net-config/config.json in os-apply-config 2018-03-27 18:07:12 +00:00
image-yaml Don't fail tripleo-bootstrap on package installs 2019-02-13 13:17:51 -05:00
playbooks Merge "Move Octavia config opts to common config directory" into stable/queens 2018-12-15 20:24:59 +00:00
releasenotes Don't fail tripleo-bootstrap on package installs 2019-02-13 13:17:51 -05:00
roles Don't fail tripleo-bootstrap on package installs 2019-02-13 13:17:51 -05:00
scripts [Queens only] Fix syntax error. 2018-10-30 13:20:52 +01:00
tools Avoid tox_install.sh for constraints support 2017-12-02 22:47:24 +00:00
tripleo_common Workflow and action for deployment failures 2019-02-28 13:21:10 -05:00
undercloud_heat_plugins Add custom subclass to revert mapping 2018-04-18 15:02:16 +00:00
workbooks Workflow and action for deployment failures 2019-02-28 13:21:10 -05:00
zuul.d Switch scenarios to non-voting 2018-11-30 18:55:27 +00: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 Update .gitreview for stable/queens 2018-03-03 11:41:47 +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 Fix readme doc 2018-05-31 18:17:22 +00:00
babel.cfg Initial Cookiecutter Commit. 2015-04-29 13:34:49 +02:00
requirements.txt Updated from global requirements 2018-03-03 21:06:28 +00:00
setup.cfg Workflow and action for deployment failures 2019-02-28 13:21:10 -05:00
setup.py Updated from global requirements 2017-03-10 03:40:32 +00:00
sudoers Add --xattrs to sudoers. 2018-07-18 11:19:20 +00:00
test-requirements.txt Updated from global requirements 2018-01-24 01:39:30 +00:00
tox.ini Update UPPER_CONSTRAINTS_FILE for stable/queens 2018-03-03 11:41:50 +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