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.
Validations which will check that the environment meets the requirements to be able to deploy OpenShift on OpenStack.
openshift-hw-requirements: Check resources for an OpenShift on OpenStack deployment
openshift-nw-requirements: Check network requirements for an OpenShift on OpenStack deployment
Validations to run on overcloud after deploying OpenStack with Ceph.
ceph-health: Check the status of the ceph cluster
package-version: The Validation name goes here
Validations which should be executed after the Overcloud deployment has finished.
ceph-health: Check the status of the ceph cluster
container-status: Ensure container status
containerized-undercloud-docker: Verify docker containers are up and ports are open
controller-token: Verify that keystone admin token is disabled
controller-ulimits: Check controller ulimits
healthcheck-service-status: Healthcheck systemd services Check
image-serve: Verify image-serve service is working and answering
mysql-open-files-limit: MySQL Open Files Limit
neutron-sanity-check: Neutron Sanity Check
nova-event-callback: Nova Event Callback Configuration Check
nova-svirt: Check nova sVirt support
openstack-endpoints: Check connectivity to various OpenStack services
ovs-dpdk-pmd-cpus-check: Validates OVS DPDK PMD cores from all NUMA nodes.
pacemaker-status: Check the status of the pacemaker cluster
package-version: The Validation name goes here
rabbitmq-limits: Rabbitmq limits
stonith-exists: Validate stonith devices
tls-everywhere-post-deployment: Confirm that overcloud nodes are setup correctly
Validations which verify that the overcloud is in a correct state after running overcloud upgrade converge command.
Validations which verify that the overcloud is in a correct state after running overcloud upgrade prepare step.
Validations which verify that the overcloud is in a correct state before running overcloud upgrade run command.
Validations which verify that the operating system upgrade went fine in the target node.
Validations which verify that the undercloud is in a correct state after upgrading.
Validations which try to validate your OpenStack deployment after you upgrade it.
container-status: Ensure container status
image-serve: Verify image-serve service is working and answering
nova-svirt: Check nova sVirt support
openstack-endpoints: Check connectivity to various OpenStack services
package-version: The Validation name goes here
stack-health: Stack Health Check
undercloud-service-status: Verify undercloud services state before running update or upgrade
Validations to run on undercloud before deploying OpenStack with Ceph.
ceph-ansible-installed: Check if ceph-ansible is installed on the undercloud
ceph-dependencies-installed: Check if Ceph dependencies are installed
package-version: The Validation name goes here
Validations which should be executed before openstack overcloud deploy.
ceilometerdb-size: Events Database Size Check (DEPRECATED)
ceph-ansible-installed: Check if ceph-ansible is installed on the undercloud
ceph-dependencies-installed: Check if Ceph dependencies are installed
collect-flavors-and-verify-profiles: Collect and verify role flavors
default-node-count: Verify hypervisor statistics
dhcp-provisioning: DHCP on the Provisioning Network
ironic-boot-configuration: Check Ironic boot configuration
network-environment: Validate the Heat environment file for network configuration
node-disks: Check node disk configuration
package-version: The Validation name goes here
switch-vlans: Compare switch port VLANs to VLANs in nic config
system_encoding: System encoding
tls-everywhere-pre-deployment: Confirm undercloud is setup correctly prior to overcloud deploy
undercloud-debug: Undercloud Services Debug Check
undercloud-heat-purge-deleted: Verify heat-manage purge_deleted is enabled in crontab
undercloud-process-count: Check the number of OpenStack processes on undercloud
Validations which should be run before the nodes introspection using Ironic Inspector.
check-network-gateway: Check network_gateway on the provisioning network
ctlplane-ip-range: Check the number of IP addresses available for the overcloud nodes
dhcp-introspection: DHCP on the Introspection Network
undercloud-disk-space: Verify undercloud fits the disk space requirements
undercloud-neutron-sanity-check: Undercloud Neutron Sanity Check
undercloud-tokenflush: Verify token_flush is enabled in keystone users crontab
Set of validations that check the right content for the templates passed to the overcloud upgrad converge step.
Set of validations that check the right content for the templates passed to the overcloud upgrade prepare step.
Validations which verify that the overcloud is in a correct state before running overcloud upgrade run command.
check-rhsm-version: Verify that the RSHM version configured is the right one
Validations which verify that the operating system can be upgraded in the target node
Validations which verify that the undercloud is in a correct state before upgrading.
check-rhsm-version: Verify that the RSHM version configured is the right one
Validations which try to validate your OpenStack deployment before you upgrade it.
collect-flavors-and-verify-profiles: Collect and verify role flavors
container-status: Ensure container status
containerized-undercloud-docker: Verify docker containers are up and ports are open
image-serve: Verify image-serve service is working and answering
ironic-boot-configuration: Check Ironic boot configuration
node-health: Node health check
nova-status: Nova Status Upgrade Check
openstack-endpoints: Check connectivity to various OpenStack services
package-version: The Validation name goes here
repos: Check correctness of current repositories
stack-health: Stack Health Check
system_encoding: System encoding
undercloud-disk-space-pre-upgrade: Verify undercloud fits the disk space requirements to perform an upgrade
undercloud-heat-purge-deleted: Verify heat-manage purge_deleted is enabled in crontab
undercloud-service-status: Verify undercloud services state before running update or upgrade
Validations check the hardware configuration of the Undercloud node and should be run before openstack undercloud install.
package-version: The Validation name goes here
tls-everywhere-prep: Confirm that undercloud is setup to register to IdM
undercloud-disk-space: Verify undercloud fits the disk space requirements
Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.