Book Image

OpenStack Administration with Ansible

By : Walter Bentley
Book Image

OpenStack Administration with Ansible

By: Walter Bentley

Overview of this book

Most organizations are seeking methods to improve business agility because they have realized just having a cloud is not enough. Being able to improve application deployments, reduce infrastructure downtime, and eliminate daily manual tasks can only be accomplished through some sort of automation. Packed with real-world OpenStack administrative tasks, this book will walk you through working examples and explain how these tasks can be automated using one of the most popular open source automation tools—Ansible. We will start with a brief overview of OpenStack and Ansible and highlight some best practices. Each chapter will provide an introduction to handling various Cloud Operator administration tasks such as creating multiple users/tenants, setting up Multi-Tenant Isolation, customizing your clouds quotas, taking instance snapshots, evacuating compute hosts for maintenance, and running cloud health checks, and a step-by-step tutorial on how to automate these tasks with Ansible.
Table of Contents (18 chapters)
OpenStack Administration with Ansible
Credits
About the Author
Acknowledgments
About the Reviewer
www.PacktPub.com
Preface
Index

Core OpenStack services


With all the infrastructure services covered, we can move on to the core OpenStack services. In this section, we will cover a few principles that can be used for any of the OpenStack services. This approach allows you to interchange any of the basic approaches for any service, based on your personal needs.

The first three services that I normally go in and check are Keystone, Nova, and Neutron. These services can have adverse effects on many other services within your cloud and need to be running properly to technically have a functioning cloud. While there is no distinct OpenStack command that you can use to check the Keystone service, it will become very obvious if the Keystone service is not operational, as any/all OpenStack CLI commands will fail. I personally feel that the easiest way to test our Keystone is to either log into the Horizon dashboard or issue the following Keystone CLI command:

$ keystone service-list

If you get the list of services using Keystone...