879b056058
It the 'chrony_enabled' key isn't found by hiera, the validation will now proceed as if it was disabled. This should allow for successful run on clouds with mix of ntp implementations. Resolves: rhbz#2156049 Signed-off-by: Jiri Podivin <jpodivin@redhat.com> Change-Id: Ic9860b3531639e85926f5221cd9c5cde03eecfa8 |
||
|---|---|---|
| .config/molecule | ||
| doc | ||
| playbooks | ||
| releasenotes | ||
| roles | ||
| scripts | ||
| tests | ||
| tools | ||
| validations_common | ||
| .ansible-lint | ||
| .coveragerc | ||
| .dockerignore | ||
| .gitignore | ||
| .gitreview | ||
| .pre-commit-config.yaml | ||
| .reqcheck_override.yaml | ||
| .stestr.conf | ||
| .yamllint | ||
| .zuul.yaml | ||
| CONTRIBUTING.rst | ||
| LICENSE | ||
| MANIFEST.in | ||
| README.rst | ||
| ansible-collections-requirements.yml | ||
| ansible-test-env.rc | ||
| bindep.txt | ||
| molecule-requirements.txt | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements.txt | ||
| tox.ini | ||
README.rst
Validations-common
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.
- Free software: Apache_license
- Documentation: https://docs.openstack.org/validations-common/latest/
- Release notes: https://docs.openstack.org/releasenotes/validations-commons/
- Source: https://opendev.org/openstack/validations-common
- Bugs - Upstream: https://bugs.launchpad.net/tripleo/+bugs?field.tag=validations
- Bugs - Downstream: https://bugzilla.redhat.com/buglist.cgi?component=validations-common&product=Red%20Hat%20OpenStack
Installation
Recommended process
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.
$ python3 -m pip install validations-commonOr, if you have virtualenvwrapper installed.
$ mkvirtualenv validations-common
$ python3 -m pip install validations-commonInstallation with package manager
Alternatively it is possible to install validations-common using package manager.
Such as yum or dnf...
$ yum|dnf install validations-commonor the more modern dnf.
$ dnf install validations-commonUsage
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.
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=8989The callback will post JSON log to the URL provided. This repository has a simple HTTP server for testing purpose under:
tools/http_server.pyThe default host and port are localhost and 8989, feel free to adjust those values to your needs.
Running the molecule tests
In order to run the molecule tests locally on your local machine, please follow the instructions documented in the Tripleo Validations Developers Guide.