pre-introspection¶
check-network-gateway¶
Check network_gateway on the provisioning network.
If gateway in undercloud.conf is different from local_ip, verify that the gateway exists and is reachable.
- hosts: undercloud
- groups: pre-introspection
- parameters:
- roles: check-network-gateway
Role documentation
ctlplane-ip-range¶
Check the number of IP addresses available for the overcloud nodes.
Verify that the number of IP addresses defined in dhcp_start and dhcp_end fields in undercloud.conf is not too low.
- hosts: undercloud
- groups: pre-introspection
- parameters:
- ctlplane_iprange_min_size: 25
- roles: ctlplane-ip-range
Role documentation
dhcp-introspection¶
DHCP on the Introspection Network.
An unexpected DHCP server on the network used for node introspection can cause some nodes to not be inspected. This validations checks for the DHCP responses on the interface specified in ironic-inspector.conf.
- hosts: undercloud
- groups: pre-introspection
- parameters:
- roles: dhcp-validations
Role documentation
undercloud-cpu¶
Verify undercloud fits the CPU core requirements.
Make sure that the undercloud has enough CPU cores. https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/15/html/director_installation_and_usage/planning-your-undercloud#determining-environment-scale
- hosts: undercloud
- groups: prep, pre-introspection
- parameters:
- min_undercloud_cpu_count: 8
- roles: undercloud-cpu
Role documentation
undercloud-disk-space¶
Verify undercloud fits the disk space requirements.
Make sure that the root partition on the undercloud node has enough free space. http://tripleo.org/install/environments/baremetal.html#minimum-system-requirements
- hosts: undercloud
- groups: prep, pre-introspection
- parameters:
- volumes: [{‘mount’: ‘/var/lib/docker’, ‘min_size’: 10}, {‘mount’: ‘/var/lib/config-data’, ‘min_size’: 3}, {‘mount’: ‘/var/log’, ‘min_size’: 3}, {‘mount’: ‘/usr’, ‘min_size’: 5}, {‘mount’: ‘/var’, ‘min_size’: 20}, {‘mount’: ‘/’, ‘min_size’: 25}]
- roles: undercloud-disk-space
Role documentation
undercloud-neutron-sanity-check¶
Undercloud Neutron Sanity Check.
Run neutron-sanity-check on the undercloud node to find out potential issues with Neutron’s configuration. The tool expects all the configuration files that are passed to the Neutron services.
- hosts: undercloud
- groups: pre-introspection
- parameters:
- configs: [‘/etc/neutron/neutron.conf’, ‘/usr/share/neutron/neutron-dist.conf’, ‘/etc/neutron/metadata_agent.ini’, ‘/etc/neutron/dhcp_agent.ini’, ‘/etc/neutron/plugins/ml2/openvswitch_agent.ini’, ‘/etc/neutron/fwaas_driver.ini’, ‘/etc/neutron/l3_agent.ini’, ‘/usr/share/neutron/neutron-lbaas-dist.conf’, ‘/etc/neutron/lbaas_agent.ini’]
- roles: neutron-sanity-check
Role documentation
undercloud-ram¶
Verify the undercloud fits the RAM requirements.
Verify that the undercloud has enough RAM. https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/15/html/director_installation_and_usage/planning-your-undercloud#determining-environment-scale
- hosts: undercloud
- groups: prep, pre-introspection, pre-upgrade
- parameters:
- min_undercloud_ram_gb: 24
- roles: undercloud-ram
Role documentation
undercloud-selinux-mode¶
Undercloud SELinux Enforcing Mode Check.
Check if the Undercloud is running SELinux in Enforcing mode.
- hosts: undercloud
- groups: prep, pre-introspection
- parameters:
- roles: undercloud-selinux-mode
Role documentation
undercloud-tokenflush¶
Verify token_flush is enabled in keystone users crontab.
Without a token_flush crontab enabled for the keystone user, the keystone database can grow very large. This validation checks that the keystone token_flush crontab has been set up.
- hosts: undercloud
- groups: pre-introspection
- parameters:
- cron_check: keystone-manage token_flush
- roles: undercloud-tokenflush
Role documentation
Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.