post-deployment¶
ceph-health¶
Check the status of the ceph cluster.
Uses ceph health to check if cluster is in HEALTH_WARN state and prints a debug message.
- hosts: Controller
- groups: post-deployment
- metadata:
- parameters:
controller-token¶
Verify that keystone admin token is disabled.
This validation checks that keystone admin token is disabled on both undercloud and overcloud controller after deployment.
- hosts: undercloud, Controller
- groups: post-deployment
- metadata:
- parameters:
controller-ulimits¶
Check controller ulimits.
This will check the ulimits of each controller.
- hosts: Controller
- groups: post-deployment
- metadata:
- parameters:
- nofiles_min: 1024
- nproc_min: 2048
haproxy¶
HAProxy configuration.
Verify the HAProxy configuration has recommended values.
- hosts: Controller
- groups: post-deployment
- metadata:
- parameters:
- config_file: /etc/haproxy/haproxy.cfg
- defaults_timeout_queue: 2m
- defaults_timeout_server: 2m
- global_maxconn_min: 20480
- defaults_maxconn_min: 4096
- defaults_timeout_client: 2m
- defaults_timeout_check: 10s
mysql-open-files-limit¶
MySQL Open Files Limit.
Verify the open-files-limit configuration is high enough https://access.redhat.com/solutions/1598733
- hosts: Controller
- groups: post-deployment
- metadata:
- parameters:
- min_open_files_limit: 16384
neutron-sanity-check¶
Neutron Sanity Check.
Run neutron-sanity-check on the controller nodes to find out potential issues with Neutron’s configuration. The tool expects all the configuration files that are passed to the Neutron services.
- hosts: Controller
- groups: post-deployment
- metadata:
- parameters:
- configs: [‘/etc/neutron/neutron.conf’, ‘/usr/share/neutron/neutron-dist.conf’, ‘/etc/neutron/metadata_agent.ini’, ‘/etc/neutron/metering_agent.ini’, ‘/etc/neutron/dhcp_agent.ini’, ‘/etc/neutron/plugins/ml2/openvswitch_agent.ini’, ‘/etc/neutron/conf.d/ml2_conf_cisco.ini’, ‘/etc/neutron/conf.d/cisco_cfg_agent.ini’, ‘/etc/neutron/conf.d/cisco_router_plugin.ini’, ‘/usr/share/neutron/l3_agent’, ‘/etc/neutron/conf.d/common’, ‘/etc/neutron/conf.d/neutron-l3-agent’, ‘/usr/share/neutron/neutron-lbaas-dist.conf’, ‘/etc/neutron/lbaas_agent.ini’, ‘/etc/neutron/conf.d/neutron-lbaas-agent’, ‘/etc/neutron/conf.d/neutron-lbaasv2-agent’, ‘/etc/neutron/conf.d/neutron-metadata-agent’, ‘/etc/neutron/conf.d/neutron-metering-agent’, ‘/etc/neutron/conf.d/neutron-netns-cleanup’, ‘/etc/neutron/conf.d/neutron-openvswitch-agent’, ‘/etc/neutron/conf.d/neutron-ovs-cleanup’, ‘/etc/neutron/conf.d/neutron-bsn-agent’, ‘/etc/neutron/conf.d/neutron-cisco-cfg-agent’, ‘/etc/neutron/conf.d/neutron-dhcp-agent’]
no-op-firewall-nova-driver¶
Verify NoOpFirewallDriver is set in Nova.
When using Neutron, the firewall_driver option in Nova must be set to NoopFirewallDriver.
- hosts: Compute
- groups: post-deployment
- metadata:
- parameters:
ntpstat¶
Verify all deployed nodes have their clock synchronised..
Each overcloud node should have their clocks synchronised. The deployment should configure and run ntpd. This validation verifies that it is indeed running and connected to an NPT server on all nodes.
- hosts: overcloud
- groups: post-deployment
- metadata:
- parameters:
openstack-endpoints¶
Check connectivity to various OpenStack services.
This validation gets the PublicVip address from the deployment and tries to access Horizon and get a Keystone token.
- hosts: undercloud
- groups: post-deployment, pre-upgrade, post-upgrade
- metadata:
- parameters:
pacemaker-status¶
Check the status of the pacemaker cluster.
This runs pcs status and checks for any failed actions. A failed status post-deployment indicates something is not configured correctly. This should also be run before upgrade as the process will likely fail with a cluster that’s not completely healthy.
- hosts: Controller
- groups: post-deployment
- metadata:
- parameters:
rabbitmq-limits¶
Rabbitmq limits.
Make sure the rabbitmq file descriptor limits are set to reasonable values.
- hosts: Controller
- groups: post-deployment
- metadata:
- parameters:
- min_fd_limit: 16384
stonith-exists¶
stonith-exists.
Verify that stonith devices are configured for your OpenStack Platform HA cluster. We don’t configure stonith device with TripleO Installer. Because the hardware configuration may be differ in each environment and requires different fence agents. How to configure fencing please read https://access.redhat.com/documentation/en/red-hat-openstack-platform/8/paged/director-installation-and-usage/86-fencing-the-controller-nodes
- hosts: Controller
- groups: post-deployment
- metadata:
- parameters:
Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.