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 template errors

Once you have confirmed that the heat-api and heat-engine processes are running as expected, and your authentication credentials are correct in Keystone and the heat.conf file, you should be able to start creating stacks. The details on how to create a Heat stack are beyond the scope of this book; however, once you have created a stack, you can check its progress by running the heat stack-list command. The output of the column titled stack_status will indicate whether or not the stack has been successfully launched. If, for some reason, your stack does not get completed successfully, stack_status will be equal to CREATE_FAILED, as demonstrated in the following screenshot:

If you have a failed stack, you can begin to troubleshoot the failure using the event-list command of heat. This command will output the steps heat has followed to create the stack and any errors heat encountered in the process.