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

Heat services

A properly running Heat installation will have at least two processes: the Heat API process (heat-api) and the Heat engine (heat-engine). In addition, you can also optionally run the Heat Cloud Formation compatibility API (heat-api-cfn). This API makes heat compatible with the API provided by the AWS Cloud Formation product. You can confirm that these processes are running by executing the following command:

ps –aux | grep heat

This command should return an output similar to the following output:

You can also leverage the pgrep command to check the Heat processes:

pgrep –l heat

The output from this command will be similar to the following output:

Running heat-api

One way to confirm that the heat-api process is running as expected is to use the Heat command-line tool. For example, you can execute the stack-list command to check this:

heat stack-list

When the heat-api process runs as expected, this command returns a list of your current stacks or an empty list if you haven't created...