Recommendations for Large Deployments

Red Hat OpenStack Platform 14

Hardware requirements and configuration for deploying OpenStack Platform at scale

OpenStack Documentation Team

Abstract

This guide contains several recommendations for deploying Red Hat OpenStack Platform at scale. These recommendations include hardware recommendations, undercloud tuning, and overcloud configuration.

Chapter 1. Introduction

This document contains information about the recommended undercloud and overcloud specifications and configuration for deploying a large Red Hat OpenStack Platform environment.

Chapter 4. Debugging tips

4.1. Introspection debugging

  • Check your introspection DHCP range and NICs in your undercloud.conf file. If either of these values are incorrect, fix them and rerun the openstack undercloud install command.
  • Ensure you are not trying to introspect more than your DHCP range of nodes can allow. Also remember that the DHCP lease for each node will still be active for approximately two minutes after introspection finishes.
  • If all nodes fail introspection, ensure that you can ping target nodes over the native VLAN using the configured NIC and that the out-of-band interface credentials and addresses are correct.
  • For debugging specific nodes, watch the console when the node boots and observe introspection commands to the node. If the node stops before completing the PXE process, check the connectivity, IP allocation, and the network load. When a node exits the BIOS and boots the introspection image, failures are rare and almost exclusively connectivity issues. Ensure that the heartbeat from the introspection image is not interrupted on its way to the undercloud.

4.2. Deployment debugging

  • Any additional DHCP servers that supply addresses on the provisioning network can prevent director from inspecting and provisioning machines.
  • For DHCP or PXE issues:

    • For introspection issues, run the following command:

      sudo tcpdump -i any port 67 or port 68 or port 69
    • For deployment issues, run:

      sudo ip netns exec qdhcp tcpdump -i <interface> port 67 or port 68 or port 69
  • For failed or foreign disks, be aware of disks that do not have an Up state according to the machine’s out-of-band management. Disks can exit the Up state during a deployment cycle and change the order that your disks appear in the base operating system.
  • Use the following commands to debug failed overcloud deployments:

    • openstack stack failures list overcloud
    • heat resource-list -n5 overcloud | grep -i fail
    • less /var/lib/mistral/config-download-latest/ansible.log

    Review the output, log into the node where the failure occurs, and review the log files in /var/log/ and /var/log/containers/.

Legal Notice

Copyright © 2019 Red Hat, Inc.
The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version.
Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the United States and other countries.
Java® is a registered trademark of Oracle and/or its affiliates.
XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
Node.js® is an official trademark of Joyent. Red Hat Software Collections is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
The OpenStack® Word Mark and OpenStack logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community.
All other trademarks are the property of their respective owners.