RETIRED, A collection of Ansible playbooks to detect and report potential issues during TripleO deployments
Go to file
Jaganathan Palanisamy 6a33ed7aa7 Validation for no PMD cores on a NUMA node
Add a validation to fail the deployment when 0 PMD cores
on a NUMA node.
When there is no PMD cores assigned to a NUMA node on
the DPDK compute node, the deployment will succeed,
but will face issues after the guest VM is created.

Change-Id: I19ff82c7737283da942649936f74fa041ee8c8ae
Closes-Bug: #1747616
(cherry picked from commit c847f0632f)
(cherry picked from commit 0a54d6de24)
2018-11-15 08:37:55 +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 Merge "Explicitly set default to 0 for quiet argument in validate-files script" 2017-12-13 19:10:22 +00:00
tripleo_validations Validation for no PMD cores on a NUMA node 2018-11-15 08:37:55 +00:00
validations Validation for no PMD cores on a NUMA node 2018-11-15 08:37:55 +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 Update .gitreview for stable/queens 2018-03-03 11:45:00 +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 Update UPPER_CONSTRAINTS_FILE for stable/queens 2018-03-03 11:45:02 +00: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.