Book Image

Troubleshooting OpenStack

By : Tony Campbell
Book Image

Troubleshooting OpenStack

By: Tony Campbell

Overview of this book

OpenStack is a collection of software projects that work together to provide a cloud fabric. OpenStack is one of the fastest growing open source projects in history that unlocks cloud computing for everyone. With OpenStack, you are able to create public or private clouds on your own hardware. The flexibility and control afforded by OpenStack puts the cloud within reach of anyone willing to learn this technology. Starting with an introduction to OpenStack troubleshooting tools, we’ll walk through each OpenStack service and how you can quickly diagnose, troubleshoot, and correct problems in your OpenStack. Understanding the various projects and how they interact is essential for anyone attempting to troubleshoot an OpenStack cloud. We will start by explaining each of the major components and the dependencies between them, and move on to show you how to identify and utilize an effective set of OpenStack troubleshooting tools and fix common Keystone problems. Next, we will expose you to common errors and problems you may encounter when using the OpenStack Block Storage service (Cinder). We will then examine Heat, the OpenStack Orchestration Service, where you will learn how to trace errors, determine their root cause, and effectively correct the issue. Finally, you will get to know the best practices to architect your OpenStack cloud in order to achieve optimal performance, availability, and reliability.
Table of Contents (17 chapters)
Troubleshooting OpenStack
About the Author
About the Reviewer


As we saw throughout this book, OpenStack deployments run multiple services. Each service typically runs multiple Linux processes. If you find yourself troubleshooting OpenStack, you should always make sure that the expected services are up and running. This is the equivalent of making sure that everything is plugged in. Monitoring the Linux processes for each service may save you a ton of headaches when it comes to troubleshooting.

Monitoring service processes

You should consider monitoring the key processes for each service. This could be as simple as configuring your monitoring service to run ps --aux on the service at regular intervals to ensure that the process is alive. Another option is to use a monitoring library that supports process monitoring and the ability to automatically restart services if they crash. Deploying methods that allow monitoring and automatic recovery of the OpenStack processes will save you time and headaches as you troubleshoot.

Backing up services

To assist...