|Zuul 0947183c34||4 weeks ago|
|.ansible-lint_rules||1 year ago|
|doc||2 months ago|
|playbooks||1 month ago|
|releasenotes||11 months ago|
|roles||5 months ago|
|scripts||1 month ago|
|tests||1 month ago|
|tools||3 months ago|
|validations_common||4 weeks ago|
|.ansible-lint||1 year ago|
|.coveragerc||1 month ago|
|.gitignore||1 month ago|
|.gitreview||1 year ago|
|.pre-commit-config.yaml||1 year ago|
|.stestr.conf||3 months ago|
|.yamllint||1 year ago|
|.zuul.yaml||3 months ago|
|CONTRIBUTING.rst||3 months ago|
|LICENSE||1 year ago|
|MANIFEST.in||1 year ago|
|README.rst||1 month ago|
|ansible-test-env.rc||1 month ago|
|bindep.txt||1 month ago|
|molecule-requirements.txt||1 month ago|
|requirements.txt||8 months ago|
|setup.cfg||3 months ago|
|setup.py||1 year ago|
|test-requirements.txt||5 months ago|
|tox.ini||1 month 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
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.
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.