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.
Bob Fournier 6d3471699c Set validation defaults to match undercloud default settings 7 months ago
doc/source Fix documentations for pypi 2 years ago
releasenotes Validate that there should not be XFS volumes with ftype=0 2 years ago
scripts Revert "Fail if the Overcloud inventory is empty" 1 year ago
tools Fix ctlplane-ip-range validations 11 months ago
tripleo_validations Validation for no PMD cores on a NUMA node 1 year ago
validations Set validation defaults to match undercloud default settings 7 months ago
zuul.d import zuul job settings from project-config 1 year ago
.coveragerc Initial Cookiecutter Commit. 4 years ago
.gitignore Add Ansible specific files to .gitignore 2 years ago
.gitreview OpenDev Migration Patch 1 year ago
.mailmap Initial Cookiecutter Commit. 4 years ago
.testr.conf Initial Cookiecutter Commit. 4 years ago
CONTRIBUTING.rst Use tripleo bug tracker on launchpad 3 years ago
HACKING.rst Initial Cookiecutter Commit. 4 years ago
LICENSE Initial Cookiecutter Commit. 4 years ago
MANIFEST.in Initial Cookiecutter Commit. 4 years ago
README.rst Fix documentations for pypi 2 years ago
ansible.cfg Add a validation-specific Ansible output callback 3 years ago
babel.cfg Initial Cookiecutter Commit. 4 years ago
hosts.sample Documentation how validations work 3 years ago
requirements.txt Updated from global requirements 2 years ago
setup.cfg Update URL home-page in documents according to document migration 2 years ago
setup.py Updated from global requirements 3 years ago
test-requirements.txt Updated from global requirements 2 years ago
tox.ini Update UPPER_CONSTRAINTS_FILE for stable/queens 2 years ago

README.rst

Team and repository tags

image

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.