About Group

For now, the validations are grouped by the deployment stage they should be run on. A validation can belong to multiple groups.

Adding a new group

To add a new group, you will need to edit the groups.yaml file located in the root of the TripleO Validations directory:

...
pre-update:
  - description: >-
      Validations which try to validate your OpenStack deployment before you
      update it.
...

And a new entry in the sphinx documentation index doc/source/index.rst:

Existing validations
====================

.. toctree::
  :maxdepth: 2

  validations-no-op-details
  validations-prep-details
  validations-pre-introspection-details
  validations-pre-deployment-details
  validations-post-deployment-details
...

Group list

Here is a list of groups and their associated validations.

No-op:

Validations which will run a no-op operation to verify that the workflow is working as it supposed to, it will run in both the Undercloud and Overcloud Nodes.

Openshift-on-openstack:

Validations which will check that the environment meets the requirements to be able to deploy OpenShift on OpenStack.

Post-ceph:

Validations to run on overcloud after deploying OpenStack with Ceph.

Post-deployment:

Validations which should be executed after the Overcloud deployment has finished.

Post-overcloud-converge:

Validations which verify that the overcloud is in a correct state after running overcloud upgrade converge command.

Post-overcloud-prepare:

Validations which verify that the overcloud is in a correct state after running overcloud upgrade prepare step.

Post-overcloud-upgrade:

Validations which verify that the overcloud is in a correct state before running overcloud upgrade run command.

Post-system-upgrade:

Validations which verify that the operating system upgrade went fine in the target node.

Post-undercloud-upgrade:

Validations which verify that the undercloud is in a correct state after upgrading.

Post-update:

Validations which should be run to validate your OpenStack deployment after you update it.

Post-upgrade:

Validations which try to validate your OpenStack deployment after you upgrade it.

Pre-ceph:

Validations to run on undercloud before deploying OpenStack with Ceph.

Pre-deployment:

Validations which should be executed before **openstack overcloud deploy*.*

Pre-introspection:

Validations which should be run before the nodes introspection using Ironic Inspector.

Pre-overcloud-converge:

Set of validations that check the right content for the templates passed to the overcloud upgrad converge step.

Pre-overcloud-prepare:

Set of validations that check the right content for the templates passed to the overcloud upgrade prepare step.

Pre-overcloud-upgrade:

Validations which verify that the overcloud is in a correct state before running overcloud upgrade run command.

Pre-system-upgrade:

Validations which verify that the operating system can be upgraded in the target node

Pre-undercloud-upgrade:

Validations which verify that the undercloud is in a correct state before upgrading.

Pre-update:

Validations which should be run to validate your OpenStack deployment before you update it.

Pre-update-converge:

Validations which should be run to verfiy containers and services are ready for pre-deployment.

  • compute-tsx: RHEL8.x kernel flag for Compute nodes validation

Pre-update-prepare:

Validations which should be run to verify undercloud updated correctly.

  • compute-tsx: RHEL8.x kernel flag for Compute nodes validation

Pre-update-run:

Validations which should be run to verify image and registration of the overcloud nodes.

  • compute-tsx: RHEL8.x kernel flag for Compute nodes validation

Pre-upgrade:

Validations which try to validate your OpenStack deployment before you upgrade it.

Prep:

Validations check the hardware configuration of the Undercloud node and should be run before **openstack undercloud install*.*