openstack
/
tripleo-validations
Code Issues Proposed changes
RETIRED, A collection of Ansible playbooks to detect and report potential issues during TripleO deployments
1,207 Commits 3 Branches 22 Tags 24 MiB
Go to file
Sagi Shnaidman 93d34a2aba Use collections in validations for Ansible 2.11 
Change-Id: Iff0f37b1a76d81df7e5b20d76cefd0c879a150f6
 		2021-10-05 10:58:50 -04:00
.ansible-lint_rules Ansible lint custom rule expansion 2021-07-29 08:25:56 +02:00
.config/molecule Introduce new Ansible validation_init role. 2021-06-04 11:16:45 +02:00
callback_plugins Remove callback plugin from tripleo-validation 2020-09-23 11:35:21 +02:00
ci/playbooks Use collections in validations for Ansible 2.11 2021-10-05 10:58:50 -04:00
doc Merge "remove using containers-prepare-parameter.yaml" 2021-07-29 14:50:26 +00:00
library Merge "Moved 'six' import to the top." 2021-09-01 18:38:16 +00:00
lookup_plugins Use the default flavor name when flavor parameter is not defined 2020-10-26 14:00:01 +09:00
playbooks Fail validation if pacemaker service is not active 2021-08-26 03:29:41 +00:00
releasenotes Merge "Removes deprecated 'overcloudrc' module" 2021-06-16 20:19:24 +00:00
roles Use collections in validations for Ansible 2.11 2021-10-05 10:58:50 -04:00
scripts Fix Inventory Generation without Overcloud deployed 2021-07-29 15:45:11 +02:00
tests Move back tripleo_validator.py to tripleoclient 2021-03-24 16:52:38 +01:00
tools Python tests are now run trough stestr. 2021-03-10 11:38:34 +01:00
tripleo_validations EndpointNotFound is now handled gracefully 2021-07-23 12:08:11 +00:00
zuul.d Add zuul.d/molecule.yaml file back in the yamllint ignore list 2021-07-05 15:42:19 +02:00
.ansible-lint Use collections in validations for Ansible 2.11 2021-10-05 10:58:50 -04:00
.coveragerc Coverage considers other all main source folders, omits tests 2021-04-07 07:13:38 +00:00
.gitignore Test folder structure rearranged. 2021-04-19 13:23:31 +02:00
.gitreview OpenDev Migration Patch 2019-04-19 19:30:05 +00:00
.mailmap Initial Cookiecutter Commit. 2016-05-27 15:00:12 +02:00
.pre-commit-config.yaml Use collections in validations for Ansible 2.11 2021-10-05 10:58:50 -04:00
.stestr.conf Python tests are now run trough stestr. 2021-03-10 11:38:34 +01:00
.testr.conf Initial Cookiecutter Commit. 2016-05-27 15:00:12 +02:00
.yamllint Add zuul.d/molecule.yaml file back in the yamllint ignore list 2021-07-05 15:42:19 +02:00
CONTRIBUTING.rst Update Validations Framework IRC channels 2021-06-04 09:46:27 +02:00
HACKING.rst Update the doc links to the newest ones 2018-03-14 01:19:54 -07:00
LICENSE Initial Cookiecutter Commit. 2016-05-27 15:00:12 +02:00
MANIFEST.in Initial Cookiecutter Commit. 2016-05-27 15:00:12 +02:00
README.rst Quick documentation content reorganization 2021-04-30 06:24:30 +02:00
ansible-collections-requirements.yml Use collections in validations for Ansible 2.11 2021-10-05 10:58:50 -04:00
ansible-test-env.rc Use the UBI8 image for testing 2020-11-20 13:45:02 +01:00
ansible.cfg Update role-addition.yml playbook to manage molecule.yaml file again 2020-12-15 10:18:45 +01:00
babel.cfg Initial Cookiecutter Commit. 2016-05-27 15:00:12 +02:00
bindep.txt Remove apk and references from bindep.txt 2021-03-19 17:36:21 +01:00
groups.yaml Adding backup-and-restore validation group 2021-04-29 11:15:24 +01:00
hosts.sample Documentation how validations work 2016-08-01 15:20:52 +02:00
molecule-requirements.txt Use collections in validations for Ansible 2.11 2021-10-05 10:58:50 -04:00
requirements.txt Filling in license info for dependencies. 2021-06-14 15:54:41 +02:00
role-addition.yml Introduce new Ansible validation_init role. 2021-06-04 11:16:45 +02:00
setup.cfg setup.cfg: Replace dashes with underscores 2021-05-08 08:39:08 +08:00
setup.py Cleanup py27 support 2020-04-13 19:03:51 +02:00
test-requirements.txt Dependency reorganization 2021-09-06 13:33:47 +02:00
tox.ini Use collections in validations for Ansible 2.11 2021-10-05 10:58:50 -04:00

README.rst

image

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 Validation Framework Command Line Interface (CLI) or by Ansible directly.