Remove legacy tripleo-validations configurations

This patch removes:
* legacy tripleo-validations config boolean, since now the role
  is in tripleo-validations repos and is enabling by another
  configuration in the zuul config directly
* documentation, because its now outdated and a new one should
  be moved under tripleo-validations repos

Change-Id: Ibc5e1aec08643d53760953ebb1c026e99689a2b6
This commit is contained in:
matbu 2021-04-12 12:11:05 +02:00 committed by mbu
parent 300a848b96
commit b43e41f401
14 changed files with 0 additions and 148 deletions

View File

@ -3,14 +3,6 @@ ssl_overcloud: false
test_ping: true
deployed_server: true
# This enables the run of several tripleo-validations tests through Mistral
run_tripleo_validations: true
# This enables the run of tripleo-validations negative tests through shell
# scripts
run_tripleo_validations_negative_tests: true
# Exit tripleo-quickstart on validations failure
exit_on_validations_failure: false
composable_scenario: multinode.yaml
composable_services: false
# Use default test template

View File

@ -1,14 +1,6 @@
undercloud_generate_service_certificate: false
enable_opstools_repo: true
# This enables the run of several tripleo-validations tests through Mistral
run_tripleo_validations: true
# This enables the run of tripleo-validations negative tests through shell
# scripts
run_tripleo_validations_negative_tests: true
# Exit tripleo-quickstart on validations failure
exit_on_validations_failure: false
deployed_server: true
composable_scenario: scenario001-multinode.yaml
composable_roles: true

View File

@ -1,13 +1,5 @@
undercloud_generate_service_certificate: false
# This enables the run of several tripleo-validations tests through Mistral
run_tripleo_validations: true
# This enables the run of tripleo-validations negative tests through shell
# scripts
run_tripleo_validations_negative_tests: true
# Exit tripleo-quickstart on validations failure
exit_on_validations_failure: false
# pacemaker settings are configured in the scenario template
# do not set `enable_pacemaker` in the featureset

View File

@ -1,13 +1,5 @@
undercloud_generate_service_certificate: false
# This enables the run of several tripleo-validations tests through Mistral
run_tripleo_validations: true
# This enables the run of tripleo-validations negative tests through shell
# scripts
run_tripleo_validations_negative_tests: true
# Exit tripleo-quickstart on validations failure
exit_on_validations_failure: false
# pacemaker settings are configured in the scenario template
# do not set `enable_pacemaker` in the featureset

View File

@ -1,13 +1,5 @@
undercloud_generate_service_certificate: false
# This enables the run of several tripleo-validations tests through Mistral
run_tripleo_validations: true
# This enables the run of tripleo-validations negative tests through shell
# scripts
run_tripleo_validations_negative_tests: true
# Exit tripleo-quickstart on validations failure
exit_on_validations_failure: false
# pacemaker settings are configured in the scenario template
# do not set `enable_pacemaker` in the featureset

View File

@ -25,14 +25,6 @@ undercloud_generate_service_certificate: false
# This enables the deployment of the overcloud with SSL.
ssl_overcloud: false
# This enables the run of several tripleo-validations tests through Mistral
run_tripleo_validations: true
# This enables the run of tripleo-validations negative tests through shell
# scripts
run_tripleo_validations_negative_tests: true
# Exit tripleo-quickstart on validations failure
exit_on_validations_failure: false
composable_roles: true
overcloud_roles:
- name: Controller

View File

@ -10,14 +10,6 @@ use_os_tempest: false
test_white_regex: ''
# This enables the run of several tripleo-validations tests through Mistral
run_tripleo_validations: false
# This enables the run of tripleo-validations negative tests through shell
# scripts
run_tripleo_validations_negative_tests: false
# Exit tripleo-quickstart on validations failure
exit_on_validations_failure: false
deployed_server: true
composable_scenario: scenario002-multinode.yaml
upgrade_composable_scenario: scenario002-multinode-containers.yaml

View File

@ -38,10 +38,6 @@ containerized_overcloud: true
undercloud_generate_service_certificate: false
ssl_overcloud: false
run_tripleo_validations: false
run_tripleo_validations_negative_tests: false
exit_on_validations_failure: false
# extra testing disabled for now, may be enabled later depending on
# job run time
test_ping: false

View File

@ -61,9 +61,6 @@ overcloud_ssh_user: >-
# Mandatory for deployed_servers
tripleo_upgrade_validations_non_fatal: true
run_tripleo_validations: false
run_tripleo_validations_negative_tests: false
exit_on_validations_failure: false
# options below direct automatic doc generation by tripleo-collect-logs
artcl_gen_docs: true
artcl_create_docs_payload:

View File

@ -13,11 +13,6 @@ overcloud_templates_path: /usr/share/openstack-tripleo-heat-templates
undercloud_templates_path: /usr/share/openstack-tripleo-heat-templates
step_introspect: true
# Disable validations and its negative tests
run_tripleo_validations: false
run_tripleo_validations_negative_tests: false
# This enables container deployements after Pike
containerized_overcloud: >-
{% if release in ['newton', 'ocata', 'pike'] -%}

View File

@ -19,7 +19,6 @@ Contents:
devmode
devmode-ovb
design
validations
contributing
working-with-extras
rhosp

View File

@ -1,70 +0,0 @@
TripleO-Validations
===================
Introduction to TripleO-Validations
-----------------------------------
This is a collection of Ansible playbooks to detect and report potential issues
during TripleO deployments.
The validations will help to 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 `Mistral Validation framework` or by Ansible directly. They are available
independently from the UI or the command line client.
* Free software: Apache license
* Source: https://opendev.org/openstack/tripleo-validations
* Bugs: https://bugs.launchpad.net/tripleo/+bugs?field.tag=validations
Running TripleO-Validations using TripleO-Quickstart
----------------------------------------------------
TripleO-Quickstart allows you to run TripleO-Validations through the two ways of
execution (according to the introduction above). The first one is using the
`Mistral framework` and will run all the validations tests by group. The second
one is using `Ansible` directly and the goal is to run negative tests. Both are
launched through shell scripts and these scripts will be available in the
undercloud in the home directory of the unprivileged account created by
TripleO-Quickstart (by default the ``stack`` user).
Running Validations tests through Mistral
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
To enable TripleO-Validations run using `Mistral`, you need to set the
``run_tripleo_validations`` variable to ``True``. By default this variable
is set to ``False``.
By Default, Tripleo-Quickstart won't fail when a validations test will fail.
If you want to disable this behaviour, you just need to set the
``exit_on_validations_failure`` to ``True``.
.. WARNING::
Note that for most of these validations, a failure does not mean that
youll be unable to deploy or run OpenStack. But it can indicate potential
issues with long-term or production setups. If youre running an environment
for developing or testing TripleO, its okay that some validations fail.
In a production setup they should not.
To run them manually, you can run the ``run-tripleo-validations.sh``. This script
takes the name of validation group as an argument::
$ bash ./run-tripleo-validations.sh [pre-introspection|pre-deployment|post-deployment]
For more informations about each validations tests owning to these groups, you
can read:
- `pre-introspection group <https://docs.openstack.org/tripleo-validations/latest/validations-pre-introspection-details.html>`__
- `pre-deployment group <https://docs.openstack.org/tripleo-validations/latest/validations-pre-deployment-details.html>`__
- `post-deployment group <https://docs.openstack.org/tripleo-validations/latest/validations-post-deployment-details.html>`__
.. NOTE::
If you want to know more about running a single or a group of validations, please
take a look at the `<https://docs.openstack.org/tripleo-docs/latest/install/validations/validations.html>`__
Running Negative tests using Ansible
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
To enable negative tests run using `Ansible`, you need to set the
``run_tripleo_validations_negative_tests`` variable to ``True``. By default
this variable is set to ``False``.

View File

@ -56,7 +56,6 @@ features_map = {
'ffu_overcloud_upgrade': ['true', 'UPGff',
'Fast-forward Overcloud Upgrade'],
'standalone_role': ['Standalone.yaml', 'Stdln', 'Standalone Deploy'],
'run_tripleo_validations': ['true', 'Valid', 'Validations'],
'test_ping': ['true', 'PingT', 'Ping and ssh tests'],
'run_tempest': ['true', 'Temps', 'run Tempest'],
'composable_scenario': ['', 'Scen#', 'Scenario ###'],

View File

@ -243,14 +243,6 @@ non_root_chown: false
# This variable is set to true in config/environments/default_libvirt.yml
enable_port_forward_for_tripleo_ui: false
# This enables the run of several tripleo-validations tests through Mistral
run_tripleo_validations: false
# This enables the run of tripleo-validations negative tests through shell
# scripts
run_tripleo_validations_negative_tests: false
# Exit tripleo-quickstart on validations failures
exit_on_validations_failure: false
# Update undercloud and overcloud images with the repos provided via the
# release config.
update_images: false