A collection of generic ansible playbooks for the Validation Framework
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.
Zuul 36a2a11205 Merge "Remove messages very specific to CI" 20 hours ago
.config/molecule Remove workaround for tox-ansible and global molecule config 1 month ago
doc Update Validations Framework IRC channels 2 weeks ago
playbooks Reqcheck job for upstream validations-common 1 month ago
releasenotes Fix pygments style 1 year ago
roles Loop variable name conflict resolution 1 day ago
scripts [Testing Infra] Apply here the improvements done to tripleo-validations 3 months ago
tests [Testing Infra] Apply here the improvements done to tripleo-validations 3 months ago
tools File validation extended to callback_plugins, main loop optimized 1 month ago
validations_common Merge "Remove messages very specific to CI" 20 hours ago
.ansible-lint Remove RoleNames ansible-lint custom rule 2 months ago
.coveragerc Cover report omits test files 2 months ago
.dockerignore Adds dockerignore to the repo 1 month ago
.gitignore .gitignore now excludes JSON molecule logs 3 months ago
.gitreview Migrate molecule jobs from centos 7 to 8 1 year ago
.pre-commit-config.yaml Bump pre-commit repositories 2 months ago
.reqcheck_override.yaml Reqcheck job for upstream validations-common 1 month ago
.stestr.conf Make the measuring code coverage test working 4 months ago
.yamllint Move Ansible components to validations_common directory 1 year ago
.zuul.yaml Trigger molecule jobs when modifying the following files 3 weeks ago
CONTRIBUTING.rst Add validation-common documentation structure 4 months ago
LICENSE Add License File 1 year ago
MANIFEST.in Initialization of validations-common 1 year ago
README.rst Re-add documentation for http_json callback 3 months ago
ansible-test-env.rc [Testing Infra] Apply here the improvements done to tripleo-validations 3 months ago
bindep.txt [Testing Infra] Apply here the improvements done to tripleo-validations 3 months ago
molecule-requirements.txt Bump molecule to 3.3.1 3 weeks ago
requirements.txt Licences are now listed for all requirements. 1 month ago
setup.cfg Merge "Use new CLI for functionnal tests and remove validation.py script" 2 months ago
setup.py Fix pbr installation issues 1 year ago
test-requirements.txt Tests for validation.py module and helper classes 2 months ago
tox.ini Merge "Removing the 'PIP_+' string from tox.ini" 22 hours ago




A collection of Ansible roles and playbooks to detect and report potential issues during 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.


There are several different ways to install validations-common. However it is recommended to both install and use the package inside python virtual environment.

At the command line using pip.

$ pip install validations-common

Or, if you have virtualenvwrapper installed.

$ mkvirtualenv validations-common
$ pip install validations-common

Installation with package manager

Alternativelly it is possible to install validations-common using package manager.

Such as yum...

$ yum install validations-common

or the more modern dnf.

$ dnf install validations-common


Once the validations-common project has been installed, navigate to the chosen share path, usually /usr/share/ansible to access the installed roles, playbooks, and libraries.

While the validations-common can be run by itself, it nonetheless depends on Ansible and validations-libs. Therefore it isn't recommended to use only validations-common.

The validations included with validations-common are intended to be demonstrations, capable of running on most setups. But they are not meant for production environment.

Validations Callbacks

http_json callback

The callback http_json sends Validations logs and information to an HTTP server as a JSON format in order to get caught and analysed with external tools for log parsing (as Fluentd or others).

This callback inherits from validation_json the format of the logging remains the same as the other logger that the Validation Framework is using by default.

To enable this callback, you need to add it to the callback whitelist. Then you need to export your http server url and port:

export HTTP_JSON_SERVER=http://localhost
export HTTP_JSON_PORT=8989

The callback will post JSON log to the URL provided. This repository has a simple HTTP server for testing purpose under:


The default host and port are localhost and 8989, feel free to adjust those values to your needs.