Advanced Format 512e Support.
Detect whether the undercloud disks use Advanced Format. If they do, the overcloud images may fail to upload to Glance.
Role documentation
Events Database Size Check (DEPRECATED).
The undercloud’s events database can grow to a substantial size if event_time_to_live is set to a negative value (infinite limit). This validation checks event_time_to_live and fails if the variable is set to a negative value or if it has no custom setting (their value is -1 by default). WARNING! This validation is considered as deprecated since Train release
Role documentation
Check if ceph-ansible is installed on the undercloud.
Prints a message if ceph-ansible isn’t installed
Role documentation
Check if Ceph dependencies are installed.
Prints a message if a ceph dependency is missed
Role documentation
Validate requested Ceph Placement Groups.
In Ceph Lumionus and newer the Placement Group overdose protection check (https://ceph.com/community/new-luminous-pg-overdose-protection) is executed by Ceph before a pool is created. If the check does not pass, then the pool is not created. When TripleO deploys Ceph it triggers ceph-ansible which creates the pools that OpenStack needs. This validation runs the same check that the overdose protection uses to determine if the user should update their CephPools, PG count, or number of OSD. Without this check a deployer may have to wait until after Ceph is running but before the pools are created to realize the deployment will fail.
Role documentation
Collect and verify role flavors.
This validation checks the flavors assigned to roles exist and have the correct capabilities set.
Role documentation
Verify hypervisor statistics.
This validation checks that the nodes and hypervisor statistics add up.
Role documentation
DHCP on the Provisioning Network.
An unexpected DHCP server on the provisioning network can cause problems with deploying the Ironic nodes. This validation checks for DHCP responses on the undercloud’s provisioning interface (eth1 by default) and fails if there are any.
Role documentation
Verify DNS.
Verify that the DNS resolution works
Role documentation
Check Ironic boot configuration.
Check if baremetal boot configuration is correct.
Role documentation
Validate the Heat environment file for network configuration.
This validates the network environment and nic-config files that specify the overcloud network configuration and are stored in the current plan’s Swift container. The deployers are expected to write these files themselves as described in the Network Isolation guide: http://tripleo.org/advanced_deployment/network_isolation.html
Role documentation
Check node disk configuration.
Check node disk numbers and sizes and whether root device hints are set.
Role documentation
Ensure services state.
Detect services status on the target host and fails if we find a failed service.
Role documentation
Compare switch port VLANs to VLANs in nic config.
LLDP data received during introspection contains the configured VLANs for each switch port attached to the nodes interfaces. Compare the VLAN IDs set on the switch port to those configured in nic config files. Since the mapping of roles to nodes isn’t known prior to deployment, this check can only check VLANs across all switch ports, not on a particular switch port.
Role documentation
Confirm undercloud is setup correctly prior to overcloud deploy.
Checks that the undercloud has novajoin set up corectly and that we are ready to do the overcloud deploy with tls-everywhere.
Role documentation
Undercloud Services Debug Check.
The undercloud’s openstack services should _not_ have debug enabled. This will check if debug is enabled on undercloud services. If debug is enabled, the root filesystem can fill up quickly, and is not a good thing.
Role documentation
Verify heat-manage purge_deleted is enabled in crontab.
Without a purge_deleted crontab enabled, the heat database can grow very large. This validation checks that the purge_deleted crontab has been set up.
Role documentation
Check the number of OpenStack processes on undercloud.
The default settings for OpenStack is to run one process (heat-engine, keystone, etc.) per CPU core. On a machine with a lot of cores this is both unnecessary and can consume a significant amount of RAM, leading to crashes due to OOMKiller.
Role documentation
validate-selinux.
Ensures we don’t have any SELinux denials on the system
Role documentation
Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.