pre-deployment¶
ceph-dependencies-installed¶
Check if Ceph dependencies are installed.
Prints a message if a ceph dependency is missed
hosts: allovercloud
groups: pre-deployment, pre-ceph
parameters:
fail_without_deps: True
tripleo_delegate_to: {{ groups[‘allovercloud’] | default([]) }}
packages: [‘lvm2’]
roles: ceph
Role documentation
check-ntp-reachability¶
Check if the NTP pool is reachable for the time synchronization.
Time synchronization is essential for successful deployment. The chrony daemon is used for connection with the NTP pool for receiving time data, if the connection is unsuccessful the deployment fails. This validation is recommended to run if the deployment is failing on time synchronization task. This validation prints NTP servers chrony is trying to access.
hosts: undercloud
groups: pre-deployment
parameters:
roles: check_ntp_reachability
Role documentation
default-node-count¶
Verify hypervisor statistics.
This validation checks that the nodes and hypervisor statistics add up. Validation requires system installation of tripleo-ansible package.
hosts: undercloud
groups: pre-deployment
parameters:
roles: default_node_count
Role documentation
dhcp-provisioning¶
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.
hosts: undercloud
groups: pre-deployment
parameters:
roles: dhcp_validations
Role documentation
ironic-boot-configuration¶
Check Ironic boot configuration.
Check if baremetal boot configuration is correct.
hosts: localhost
groups: pre-deployment, pre-upgrade
parameters:
roles: ironic_boot_configuration
Role documentation
network-environment¶
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
hosts: undercloud
groups: pre-deployment
parameters:
network_environment_path: environments/network-environment.yaml
plan_env_path: plan-environment.yaml
ip_pools_path: environments/ips-from-pool-all.yaml
roles: network_environment
Role documentation
node-disks¶
Check node disk configuration.
Check node primary/root disk sizes and compare with flavor expectations. Fitness of other disks can be checked manually using introspection.
hosts: localhost
groups: pre-deployment
parameters:
roles: node_disks
Role documentation
package-version¶
package-version.
Ensures we can access the wanted package version. Especially useful when you are switching repositories, for instance during an upgrade.
hosts: all
groups: prep, pre-deployment, pre-upgrade, pre-update, pre-system-upgrade, pre-undercloud-upgrade, pre-overcloud-prepare, pre-overcloud-upgrade, pre-overcloud-converge, pre-ceph
parameters:
package_version_debug: False
roles: package_version
Role documentation
switch-vlans¶
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.
hosts: undercloud
groups: pre-deployment
parameters:
network_environment_path: environments/network-environment.yaml
ironic_inspector_conf_file: /var/lib/config-data/puppet-generated/ironic_inspector/etc/ironic-inspector/inspector.conf
roles: switch_vlans
Role documentation
system-encoding¶
System encoding.
Ensure the local is unicode
hosts: all
groups: pre-deployment, pre-upgrade, pre-update
parameters:
system_encoding_debug: False
roles: system_encoding
Role documentation
tls-everywhere-pre-deployment¶
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.
hosts: undercloud
groups: pre-deployment
parameters:
roles: tls_everywhere
Role documentation
undercloud-debug¶
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. This role needs to be run against an installed Undercloud. The tested services must use one of the specified configuration files to set their debug status.
hosts: undercloud
groups: pre-deployment
parameters:
debug_check: True
roles: undercloud_debug
Role documentation
undercloud-process-count¶
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.
hosts: undercloud
groups: pre-deployment
parameters:
max_process_count: 8
roles: undercloud_process_count
Role documentation