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

Multiple hypervisor support


This topic happens to be one of my favorites because I love to see the shocked faces of most folks when I say "OpenStack is not a hypervisor". Yes, I repeat, "OpenStack is NOT a hypervisor". It has to be said twice in order to make sure that the point is being driven home. A very common misunderstanding in reference to OpenStack is that it will be directly compared to other hypervisors that are popular in the market. I am not going to name them, but most of us know what/who I am referring to. From a base level, this type of comparison is similar to literally comparing apples and oranges. One of the first principles that should be made clear when working with OpenStack is that it should be seen more as a hardware and hypervisor manager. The role OpenStack has regarding the hypervisor is to manage the hypervisor's functions and report on its health. OpenStack does not honestly care which hypervisor is made available, as long as there is a code to support that particular...