RETIRED, A Python library for code common to TripleO CLI and TripleO UI.
Go to file
Florian Fuchs b6e9412628 Fix flavor matching for object-storage role
When assigning a node to the `object-storage` role, the correct flavor
will not be picked, because there is a mismatch between the role name
and the flavor name (swift-storage).

This patch adds some logic to pick the correct flavor for the object
storage role.

Change-Id: Id3d5738361f791a3e1120ad3b51d8867c27e4456
Closes-Bug: #1644756
2016-11-28 21:52:31 +01:00
contrib Upload docker image files from yaml config file 2016-03-21 12:13:14 -04:00
doc/source Remove the duplication of Workbook in the description. 2016-10-07 16:31:28 +01:00
heat_docker_agent Fix tox -epep8 for Python3 2016-11-21 14:40:21 +00:00
image-yaml Merge "Install yum-plugin-priorities on centos images" 2016-11-23 15:16:09 +00:00
scripts Merge "TrivialFix: Remove default=None when set value in Config" 2016-10-21 17:16:07 +00:00
tripleo_common Fix flavor matching for object-storage role 2016-11-28 21:52:31 +01:00
undercloud_heat_plugins Merge "Ignore changes to images in nova servers" 2016-09-27 00:13:43 +00:00
workbooks Pass the plan name when tagging nodes 2016-11-17 12:10:21 +00:00
.coveragerc Make coverage tests work 2015-11-30 23:01:07 +00:00
.gitignore Make coverage tests work 2015-11-30 23:01:07 +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 Initial Cookiecutter Commit. 2015-04-29 13:34:49 +02:00
HACKING.rst Fix formatting in doc files 2016-07-22 16:46:04 +02:00
LICENSE Initial Cookiecutter Commit. 2015-04-29 13:34:49 +02:00
MANIFEST.in Initial Cookiecutter Commit. 2015-04-29 13:34:49 +02:00
README.rst Workflows to run validations 2016-08-29 13:56:49 +02:00
babel.cfg Initial Cookiecutter Commit. 2015-04-29 13:34:49 +02:00
requirements.txt Updated from global requirements 2016-11-09 04:26:03 +00:00
setup.cfg Port Scale Down Functionality into Workflow 2016-10-14 13:29:49 +01:00
setup.py Updated from global requirements 2015-10-23 16:05:01 +00:00
sudoers Workflows to run validations 2016-08-29 13:56:49 +02:00
test-requirements.txt Remove discover from test-requirements 2016-11-16 10:38:57 +05:30
tox.ini Remove last vestiges of oslo-incubator 2016-10-26 11:04:41 +00:00

README.rst

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

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