David Vallee Delisle 4aaca32f19 Introducing the oslo_config_validator role
This role is intended to leverage the `oslo-config-validator` on each one
of the configuration files found on a deployment. The goal is to quickly
catch erroneous configurations.

When called manually, it will also be possible to generate a report
returning all the differences between the current configuration and the
default configuration

One last thing, it will also validate the values of some specific
settings, based on the invalid_settings dict in the configuration.
Because of that, we moved some checks in nova_event_callback to the
oslo_config_validator role.

Depends-On: https://review.opendev.org/c/openstack/oslo.config/+/790883
Related: https://bugzilla.redhat.com/show_bug.cgi?id=1940815
Resolves: rhbz#1940815
Change-Id: Id047fe378cf512b985c9d7478a991f11b280102b
2021-06-15 13:17:54 -04:00
2021-06-07 17:33:57 -04:00
2021-06-08 16:08:41 +05:30
2021-04-19 13:23:31 +02:00
2019-04-19 19:30:05 +00:00
2016-05-27 15:00:12 +02:00
2016-05-27 15:00:12 +02:00
2016-05-27 15:00:12 +02:00
2016-05-27 15:00:12 +02:00
2016-05-27 15:00:12 +02:00
2021-05-27 16:14:13 +02:00
2020-04-13 19:03:51 +02:00
2021-05-20 06:45:01 +02:00

image

A collection of Ansible roles and 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 Validation Framework Command Line Interface (CLI) or by Ansible directly.

Description
RETIRED, A collection of Ansible playbooks to detect and report potential issues during TripleO deployments
Readme 24 MiB