openstack
/
tripleo-common
Code Issues Proposed changes
RETIRED, A Python library for code common to TripleO CLI and TripleO UI.
889 Commits 3 Branches 35 Tags 82 MiB
Go to file
Saravanan KR 847e31069a Workflow to get the list of deprecated parameters from the plan 
Templates can have parameter_groups with label as deprecated to
specific the list of deprecated parameters. This workflow will
return the list all the deprecated parameters including nested
stacks. The sample output will look like -
[
    {
        "deprecated": true,
        "parameter": "ServiceNetMapDeprecatedMapping",
        "user_defined": false
    },
    {
        "deprecated": true,
        "parameter": "NeutronL3HA",
        "user_defined": true
    }
]

Depends-On: I032144733bde916f8de8644121b9fb1ef29baef2

Change-Id: I18430b7d7bca7c58b75569e3d296e315227e6f61
 		2017-06-14 17:13:29 +05:30
container-images Add missing haproxy container image 2017-06-13 09:39:54 +02:00
contrib Rename contrib to container-images for packaging 2017-04-07 16:56:29 +12:00
doc/source [trivial] Remove broken link 2017-02-01 18:37:58 +01:00
heat_docker_agent Remove symlinks causing hiera hook to exit early 2017-06-06 15:27:55 +02:00
image-yaml Merge "Start using generic dracut-regenerate element" 2017-06-05 14:18:47 +00:00
releasenotes Workflow to get the list of deprecated parameters from the plan 2017-06-14 17:13:29 +05:30
scripts Replace swiftclient with openstackclient 2017-05-30 23:04:38 +00:00
tools Add ReNo support 2017-01-12 12:06:02 +00:00
tripleo_common Workflow to get the list of deprecated parameters from the plan 2017-06-14 17:13:29 +05:30
undercloud_heat_plugins Replace six.iteritems() with .items() 2017-03-10 01:45:40 +00:00
workbooks Workflow to get the list of deprecated parameters from the plan 2017-06-14 17:13:29 +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-06-06 23:29:22 +00:00
setup.cfg Merge "Use Swift to store Plan environment" 2017-06-13 12:28:49 +00:00
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-06-06 23:29:22 +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