A collection of Ansible playbooks to detect and report potential issues during TripleO deployments
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
Go to file
Martin André 13582abeab
Initial Cookiecutter Commit.
7 years ago
doc/source Initial Cookiecutter Commit. 7 years ago
tripleo_validations Initial Cookiecutter Commit. 7 years ago
.coveragerc Initial Cookiecutter Commit. 7 years ago
.gitignore Initial Cookiecutter Commit. 7 years ago
.gitreview Added .gitreview 7 years ago
.mailmap Initial Cookiecutter Commit. 7 years ago
.testr.conf Initial Cookiecutter Commit. 7 years ago
CONTRIBUTING.rst Initial Cookiecutter Commit. 7 years ago
HACKING.rst Initial Cookiecutter Commit. 7 years ago
LICENSE Initial Cookiecutter Commit. 7 years ago
MANIFEST.in Initial Cookiecutter Commit. 7 years ago
README.rst Initial Cookiecutter Commit. 7 years ago
babel.cfg Initial Cookiecutter Commit. 7 years ago
requirements.txt Initial Cookiecutter Commit. 7 years ago
setup.cfg Initial Cookiecutter Commit. 7 years ago
setup.py Initial Cookiecutter Commit. 7 years ago
test-requirements.txt Initial Cookiecutter Commit. 7 years ago
tox.ini Initial Cookiecutter Commit. 7 years ago

README.rst

TripleO Validations

A collection of Ansible 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.

Prerequisites

The TripleO validations require Ansible 2.0 or above:

$ sudo pip install 'ansible>=2'