RETIRED, A collection of Ansible playbooks to detect and report potential issues during TripleO deployments
6a3081beac
This patch adds a molecule configuration file at the repository
level (tripleo-validations/.config/molecule/config.yml) which defines
all the default values for molecule.yml files in all roles.
This patch also introduces a common Dockerfile (UBI8 image) shared
between all the role molecule tests. This Dockerfile will install the
CentOS 8.x Linux Repos and GPG Keys during the image build.
This Dockerfile is located in tripleo-validations/.config/molecule
directory and it is shared through a relative symbolic link between all
the molecule directories.
NOTE: tox-ansible doesn't manage shared molecule configuration at the
project level (see [1]). To be able to use it, we have to explicitly add
the driver name in each molecule.yml file in the roles level. Once [1]
will be fixed, these will be removed.
[1] - https://github.com/ansible-community/tox-ansible/issues/88).
Signed-off-by: Gael Chamoulaud (Strider) <gchamoul@redhat.com>
Change-Id: I4717825e2767dc55016a30fb62aa6a5541f26cfd
(cherry picked from commit
|
||
---|---|---|
.ansible-lint_rules | ||
.config/molecule | ||
_skeleton_role_ | ||
callback_plugins | ||
ci/playbooks | ||
doc | ||
library | ||
lookup_plugins | ||
playbooks | ||
releasenotes | ||
roles | ||
scripts | ||
tests | ||
tools | ||
tripleo_validations | ||
zuul.d | ||
.ansible-lint | ||
.coveragerc | ||
.gitignore | ||
.gitreview | ||
.mailmap | ||
.pre-commit-config.yaml | ||
.stestr.conf | ||
.testr.conf | ||
.yamllint | ||
CONTRIBUTING.rst | ||
HACKING.rst | ||
LICENSE | ||
MANIFEST.in | ||
README.rst | ||
ansible-test-env.rc | ||
ansible.cfg | ||
babel.cfg | ||
bindep.txt | ||
groups.yaml | ||
hosts.sample | ||
molecule-requirements.txt | ||
requirements.txt | ||
role-addition.yml | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
README.rst
TripleO Validations
A collection of Ansible roles and playbooks to detect and report potential issues during TripleO deployments.
The validations will help detect issues early in the deployment process and prevent field engineers from wasting time on misconfiguration or hardware issues in their environments.
All validations are written in Ansible and are written in a way that's consumable by the Mistral validation framework or by Ansible directly. They are available independently from the UI or the command line client.
- Free software: Apache license
- Documentation: https://docs.openstack.org/tripleo-validations/latest/
- Release notes: https://docs.openstack.org/releasenotes/tripleo-validations/
- Source: https://opendev.org/openstack/tripleo-validations
- Bugs: https://storyboard.openstack.org/#!/project/openstack/tripleo-validations