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

Ceilometer processes

A working Ceilometer installation will have several processes running, some of which are as follows:

  • ceilometer-api

  • ceilometer-collector

  • ceilometer-polling

  • ceilometer-agent-notification

When troubleshooting Ceilometer, an effective place to start is ensuring that each of the preceding processes run. As we've seen before, we can verify this by running either ps -aux or pgrep on Ceilometer. Take the following command, for example:

Alternatively, you can use the pgrep command to retrieve similar information. An example is included in the following screenshot:

If any of these processes are not running as expected, you can search the log files for possible clues. The log files for Ceilometer are typically stored at /var/log/ceilometer, but you can confirm the log file location by checking the Ceilometer configuration file for the value of the log_dir variable. If the log files are empty or do not provide any clues, you can attempt to start the services manually, which will...