openstack
/
tripleo-validations
Code Issues Proposed changes
RETIRED, A collection of Ansible playbooks to detect and report potential issues during TripleO deployments
360 Commits 3 Branches 22 Tags 24 MiB
Go to file
Jose Luis Franco Arza 2cfc6c7ba7 Run validation only if overcloud exists. 
When no overcloud is deployed, the openstack-endpoint.yaml validations
fail. This patch re-orders couple of tasks and runs the failing task for
unavailable endpoints only when an overcloud exists.

Change-Id: I174b5a239a7c1ab7b93323654a417db8f087bc27
Story: #2002061
(cherry picked from commit 864ab1d64d)
 		2020-07-30 06:27:24 +00:00
doc/source Fix documentations for pypi 2018-05-30 08:38:37 -07:00
releasenotes Validate that there should not be XFS volumes with ftype=0 2018-04-26 06:59:17 +00:00
scripts Revert "Fail if the Overcloud inventory is empty" 2018-08-27 12:23:25 +02:00
tools Fix ctlplane-ip-range validations 2019-06-11 19:25:42 +10:00
tripleo_validations Validation for no PMD cores on a NUMA node 2018-11-15 08:37:55 +00:00
validations Run validation only if overcloud exists. 2020-07-30 06:27:24 +00:00
zuul.d import zuul job settings from project-config 2018-08-24 05:07:10 +00:00
.coveragerc Initial Cookiecutter Commit. 2016-05-27 15:00:12 +02:00
.gitignore Add Ansible specific files to .gitignore 2017-10-06 13:31:28 +02:00
.gitreview OpenDev Migration Patch 2019-04-19 19:30:06 +00:00
.mailmap Initial Cookiecutter Commit. 2016-05-27 15:00:12 +02:00
.testr.conf Initial Cookiecutter Commit. 2016-05-27 15:00:12 +02:00
CONTRIBUTING.rst Use tripleo bug tracker on launchpad 2016-07-27 11:04:38 +02:00
HACKING.rst Initial Cookiecutter Commit. 2016-05-27 15:00:12 +02: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 Fix documentations for pypi 2018-05-30 08:38:37 -07:00
ansible.cfg Add a validation-specific Ansible output callback 2016-10-13 14:37:42 +02:00
babel.cfg Initial Cookiecutter Commit. 2016-05-27 15:00:12 +02:00
hosts.sample Documentation how validations work 2016-08-01 15:20:52 +02:00
requirements.txt Updated from global requirements 2018-03-03 21:06:47 +00:00
setup.cfg Update URL home-page in documents according to document migration 2017-07-14 03:18:45 +00:00
setup.py Updated from global requirements 2017-03-02 17:55:09 +00:00
test-requirements.txt Updated from global requirements 2018-01-24 01:40:06 +00:00
tox.ini Use ansible-lint == 3.5.1 for stable/queens 2020-01-23 15:49:02 +01:00

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.