Callback plugins were transferred from validations-common
repository to validations-libs.
Necessary adjustments were made to the module structure,
requierements, as well as installation and documentation generator config.
Associated tests were moved as well, with removal of superfluous inheritance
and imports included.
Demonstration http server module for communication with `http_json`
callback was moved with directory structure preserved.
Signed-off-by: Jiri Podivin <jpodivin@redhat.com>
Change-Id: I31768375430a2f29da71aae8f3db3882c373ced5
Presently, the operator(s) can only execute the official and supported
validations coming from tripleo-validations and validations-common.
Community validations enable a sysadmin to create and execute
validations unique to their environment.
This patch introduces the new Command Line Interface sub command to
create a new community validation skeleton. First, this latter will
check if there is an existing role or a playbook either in the community
validations catalog or the official validations catalog. And it will
create an Ansible role (with ansible-galaxy[1]) and a playbook in the
~/community-validations directory.
By default, the community validations feature is enabled but may be
disabled by setting [DEFAULT].enable_community_validations to ``False``
in the validation configuration file.
Example:
[stack@localhost]$ validation init my-new-validation
Validation config file found: /etc/validation.cfg
New role created successfully in /home/stack/community-validations/roles/my_new_validation
New playbook created successfully in /home/stack/community-validations/playbooks/my-new-validation.yaml
For a full demo of this new CLI sub command, please take a look at this
asciinema[2].
[1] - https://docs.ansible.com/ansible/latest/cli/ansible-galaxy.html
[2] - https://asciinema.org/a/445105
Change-Id: I8fb16e3456696187d4a9d3820740a7639a96e315
Signed-off-by: Gael Chamoulaud (Strider) <gchamoul@redhat.com>
Introduce validation config file.
The config default location of the config file will be stored
in /etc/validation.cfg
The variables precedence will be the following:
* user's cli args
* config file
* default interval values
Change-Id: I05c54a43bc0a03878793cca3f51e23f4a8b63a23
Setuptools v54.1.0 introduces a warning that the use of dash-separated
options in 'setup.cfg' will not be supported in a future version [1].
Get ahead of the issue by replacing the dashes with underscores. Without
this, we see 'UserWarning' messages like the following on new enough
versions of setuptools:
UserWarning: Usage of dash-separated 'description-file' will not be
supported in future versions. Please use the underscore name
'description_file' instead
[1] https://github.com/pypa/setuptools/commit/a2e9ae4cb
Change-Id: I7be73e3e6d4cda3aa009a80dfa81b2c9bd961b48
This review adds a CLI for the Validation Framework which will become
the only entry point to run the Validation Framework.
It will deprecate the tripleo_validatior.py CLI and the
validation.py script.
This patch uses python cliff library to provide nice helpers, shell
and output formats.
Change-Id: I66800ad51cc50f4eb37efabe85fb553dce008101
After merge of 723586 anyway.
Specific changes include:
new readme.rst in doc structure
tox adjustment
license info
bugtracking and source links
date update
badges
CONTRIBUTING.rst
ansible_autodoc.py
release notes infrastructure
Signed-off-by: Jiri Podivin <jpodivin@redhat.com>
Change-Id: Ia3db253e05d0f8d754259ff841a783f29cd6a70f
The CI roles are stored on both repos:
validations-common and validations-libs.
We need to stored those roles only in one place.
This review removed the roles from validations-libs
and used it from validations-common
Change-Id: Ia343509716f0a7769c8edcd502a678927935b419
Now that we are running the Victoria tests that include a
voting py38, we can now add the Python 3.8 metadata to the
package information to reflect that support.
Change-Id: I853112437e2e9610d421cc48e16f1386a0967788
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>