openstack
/
tripleo-common-tempest-plugin
Code Issues Proposed changes
RETIRED, Tempest plugin for the tripleo-common project
13 Commits 1 Branch 0 Tags 289 KiB
Go to file
qingszhao af3d21a9b3 import zuul job settings from project-config 
This is a mechanically generated patch to complete step 1 of moving
the zuul job settings out of project-config and into each project
repository.

Because there will be a separate patch on each branch, the branch
specifiers for branch-specific jobs have been removed.

Because this patch is generated by a script, there may be some
cosmetic changes to the layout of the YAML file(s) as the contents are
normalized.

See the python3-first goal document for details:
https://governance.openstack.org/tc/goals/stein/python3-first.html

Change-Id: I5deb89b42edc20e2af893e742e7e8db5ca5bac0a
Story: #2002586
Task: #24341
 		2018-08-24 04:59:04 +00:00
tripleo_common_tempest_plugin Fix gating on tripleo-common-tempest-plugin 2017-11-08 10:10:19 +00:00
.coveragerc Create initial project layout 2017-11-03 08:25:15 +00:00
.gitignore Update the .gitignore 2017-11-15 15:01:51 +00:00
.gitreview Fix gating on tripleo-common-tempest-plugin 2017-11-08 10:10:19 +00:00
.testr.conf Create initial project layout 2017-11-03 08:25:15 +00:00
.zuul.yaml import zuul job settings from project-config 2018-08-24 04:59:04 +00:00
CONTRIBUTING.rst Create initial project layout 2017-11-03 08:25:15 +00:00
HACKING.rst Create initial project layout 2017-11-03 08:25:15 +00:00
LICENSE Create initial project layout 2017-11-03 08:25:15 +00:00
README.rst Create initial project layout 2017-11-03 08:25:15 +00:00
babel.cfg Create initial project layout 2017-11-03 08:25:15 +00:00
requirements.txt Updated from global requirements 2018-03-14 06:11:31 +00:00
setup.cfg Correct the package name in the setup.cfg 2017-11-15 15:02:03 +00:00
setup.py Create initial project layout 2017-11-03 08:25:15 +00:00
test-requirements.txt Updated from global requirements 2018-03-15 09:37:53 +00:00
tox.ini Add the tempest command check-uuid to tox.ini 2017-11-15 15:02:03 +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

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