pre-deployment¶
512e¶
Advanced Format 512e Support.
Detect whether the undercloud disks use Advanced Format. If they do, the overcloud images may fail to upload to Glance.
- hosts: undercloud
- groups: prep, pre-deployment
- metadata:
- parameters:
ceilometerdb-size¶
Ceilometer Database Size Check.
The undercloud’s ceilometer database can grow to a substantial size if metering_time_to_live and event_time_to_live is set to a negative value (infinite limit). This validation checks each setting and fails if variables are set to a negative value or if they have no custom setting (their value is -1 by default).
- hosts: undercloud
- groups: pre-deployment
- metadata:
- parameters:
- metering_ttl_check: metering_time_to_live
- event_ttl_check: event_time_to_live
ceph-ansible-installed¶
Check if ceph-ansible is installed on the undercloud.
Prints a message if ceph-ansible isn’t installed
- hosts: undercloud
- groups: pre-deployment
- metadata:
- parameters:
deployment-images¶
Verify existence of deployment images..
This validation checks that images bm-deploy-kernel and bm-deploy-ramdisk exist before deploying the overcloud.
- hosts: undercloud
- groups: pre-deployment
- metadata:
- parameters:
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
- metadata:
- parameters:
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
- metadata:
- parameters:
- network_environment_path: environments/network-environment.yaml
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.
- hosts: undercloud
- groups: pre-deployment
- metadata:
- parameters:
- debug_check: True
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
- metadata:
- parameters:
- max_process_count: 8
Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.