openstack
/
tripleo-common
Code Issues Proposed changes
RETIRED, A Python library for code common to TripleO CLI and TripleO UI.
726 Commits 3 Branches 35 Tags 82 MiB
Go to file
Steven Hardy e38bcc9f09 Workflow to select nodes matching a profile/role 
As a first step to enabling parameter calculation based on introspection
data, we'll need to find the available nodes matching a particular role
(which is associated with a flavor, which matches a specific profile in
ironic).

The next step is to retrieve the introspection data for each node output
from this workflow, then define another workflow that does the
transformation between introspection data and parameters.

Partially-Implements: blueprint tripleo-derive-parameters
Change-Id: I4b13f2923caa055be979eda57f9d5009960d61ef
 		2017-04-10 20:45:54 +05:30
contrib Rename 'uploads' key to 'container_images' 2017-03-23 10:15:44 +13:00
doc/source [trivial] Remove broken link 2017-02-01 18:37:58 +01:00
heat_docker_agent Merge "Add python-heat-agent-json-file to the heat docker agent" 2017-01-31 10:15:41 +00:00
image-yaml Remove machine-id from image 2017-03-13 14:39:06 -06:00
releasenotes Workflow to select nodes matching a profile/role 2017-04-10 20:45:54 +05:30
scripts Adds basic logging to the upgrade-non-controller.sh utility 2017-01-31 18:12:18 +02:00
tools Add ReNo support 2017-01-12 12:06:02 +00:00
tripleo_common Workflow to select nodes matching a profile/role 2017-04-10 20:45:54 +05:30
undercloud_heat_plugins Replace six.iteritems() with .items() 2017-03-10 01:45:40 +00:00
workbooks Workflow to select nodes matching a profile/role 2017-04-10 20:45:54 +05:30
.coveragerc Make coverage tests work 2015-11-30 23:01:07 +00:00
.gitignore Add ReNo support 2017-01-12 12:06:02 +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 Pin docutils version 2016-12-12 07:29:45 +01:00
babel.cfg Initial Cookiecutter Commit. 2015-04-29 13:34:49 +02:00
requirements.txt Updated from global requirements 2017-03-14 11:29:40 +00:00
setup.cfg Workflow to select nodes matching a profile/role 2017-04-10 20:45:54 +05:30
setup.py Updated from global requirements 2017-03-10 03:40:32 +00:00
sudoers Fix race in undercloud cell_v2 host discovery 2017-02-01 13:56:58 +00:00
test-requirements.txt Updated from global requirements 2017-03-02 05:08:53 +00:00
tox.ini Add Constraints support 2017-01-13 22:58:18 +01: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

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