ef6f7dad74
Now that the whole-disk image is being deployed, mounting an image using tools like kpartx or qemu-nbd is much more involved, requiring knowledge of the image LVM volumes and their intended mount points. The scripts tripleo-mount-image and tripleo-unmount-image will mount the contents of an overcloud image file using qemu-nbd, making it available for chroot, or other read/write image operations. The scripts handle partition images (overcloud-full.qcow2) as well as the whole-disk image (overcloud-hardened-uefi-full.qcow2) with its multiple LVM volume mount points. qemu-nbd was chosen over kpartx as downstream documentation[1] has standardized on this tool for mount based image modifications. tripleo-unmount-image is a symlink to tripleo-mount-image and behaves differently based on the script name. Blueprint: whole-disk-default [1] https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.1/html/bare_metal_provisioning/booting-from-cinder-volumes Change-Id: I3267b4ae5200eeed333a9518865260d23315f52c (cherry picked from commit |
||
---|---|---|
container-images | ||
contrib | ||
doc | ||
healthcheck | ||
heat_docker_agent | ||
image-yaml | ||
releasenotes | ||
scripts | ||
tools | ||
tripleo_common | ||
undercloud_heat_plugins | ||
zuul.d | ||
.coveragerc | ||
.gitignore | ||
.gitreview | ||
.mailmap | ||
.pre-commit-config.yaml | ||
.pylintrc | ||
.stestr.conf | ||
bindep.txt | ||
CONTRIBUTING.rst | ||
HACKING.rst | ||
LICENSE | ||
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