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

Cinder processes

A working Cinder installation will have several processes running. Say, for example, you run the following command:

ps –aux | grep cinder

After this, you should see an output similar to the output shown here:

You will note that there are several cinder-api processes, several cinder-volume processes, and a cinder-scheduler process. When troubleshooting Cinder, you want to make sure that these three processes are up and successfully running. If one of the processes isn't running for some reason, you can use the respective start commands given here on Ubuntu systems using upstart:

start cinder-api
start cinder-volume
start cinder-scheduler

If you have trouble starting any of the processes using the upstart scripts, you may want to try and start them manually, where you will be able to see any errors that are being thrown on startup. To start the process manually, use the following command:

sudo -u cinder cinder-api --config-file=/etc/cinder/cinder.conf --log-file=/var/log/cinder...