validations

Existing validations

Here are all the validations that currently exist. They're grouped by the deployment stage they're should be run on.

• prep: validations that are run on a fresh machine before the undercloud is installed
• pre-introspection: when the undercloud is ready to perform hardware introspection
• pre-deployment: validations that are run right before deploying the overcloud
• post-deployment: validations that are run after the overcloud deployment finished

Validations can belong to multiple groups.

Prep

• Make sure the undercloud drives have 512e support
• Detect rogue DHCP servers
• Verify the undercloud has enough CPU cores
• Verify the undercloud has enough disk space for the initial deployment
• Verify the undercloud has enough RAM

Pre-introspection

• Verify network_gateway is set correctly in undercloud.conf and is reachable
• Check the number of IP addresses for the overcloud nodes
• Validate the instackenv.json file contents
• Detect rogue DHCP servers
• Verify the undercloud has enough CPU cores
• Verify the undercloud has enough disk space for the initial deployment
• Verify the undercloud has enough RAM

Pre-deployment

• Make sure the undercloud drives have 512e support
• Highlight differences between nodes based on the discovery data from Ironic
• Validate the Heat network environment files
• Detect rogue DHCP servers
• Verify the undercloud doesn't run too many processes

Post-deployment

• Check connectivity to OpenStack services
• Verify nodes can ping the IP addresses on the isolated networks
• Verify the HAProxy configuration
• Verify MySQL Open Files limit
• Run neutron-sanity-check
• Verify Nova's firewall_driver is set to NoopFirewallDriver
• Verify all hosts have NTP configured and running
• Verify the pacemaker status on the controller nodes
• Verify the rabbitmq file descriptor limits are set correctly.
• Check ulimits on controller nodes