a54dc49bba
The state information in the ceph-ansible fetch directory is no longer necessary to replace a Ceph monitor as of ceph-ansible 4.0.14-1. Stein, Train, Ussuri and newer should be using this version of ceph-ansible or newer. TripleO does not need to do extra work to maintain the fetch directory. This means that the plan_management workbook no longer needs to create the SwiftFetchDirGetTempurl and the SwiftFetchDirPutTempurl parameters. This patch removes the create_ceph_ansible_fetch_directory_backup_plan task which creates them. It also removes the workbook rename_ceph_ansible_fetch_directory. Both Icce658f803a608ee4b7df34b0b8297ecabcdb0ee and Ifab82c9a5b0a206c14ae7976d2c1c7f0e9fa3d9d are effectively reverted of their ceph aspects with this change, but this change should not be backported to Rocky or older because ceph-ansible 3 still needs the fetch directory. Change-Id: I167449e4d7e38f0f5fd74251a3bd8f5b0b31451b Related-Bug: #1863809 |
||
---|---|---|
container-images | ||
contrib | ||
doc/source | ||
healthcheck | ||
heat_docker_agent | ||
image-yaml | ||
releasenotes | ||
scripts | ||
tools | ||
tripleo_common | ||
undercloud_heat_plugins | ||
workbooks | ||
zuul.d | ||
.ansible-lint | ||
.coveragerc | ||
.gitignore | ||
.gitreview | ||
.mailmap | ||
.pre-commit-config.yaml | ||
.stestr.conf | ||
babel.cfg | ||
bindep.txt | ||
CONTRIBUTING.rst | ||
HACKING.rst | ||
LICENSE | ||
lower-constraints.txt | ||
README.rst | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
sudoers | ||
test-requirements.txt | ||
tox.ini |
Team and repository tags
tripleo-common
A common library for TripleO workflows.
- Free software: Apache license
- Documentation: https://docs.openstack.org/tripleo-common/latest/
- Source: http://opendev.org/openstack/tripleo-common
- Bugs: https://bugs.launchpad.net/tripleo-common
- Release notes: https://docs.openstack.org/releasenotes/tripleo-common
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://opendev.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