Book Image

OpenStack Administration with Ansible 2 - Second Edition

Book Image

OpenStack Administration with Ansible 2 - Second Edition

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. We start with a brief overview of OpenStack and Ansible 2 and highlight some best practices. Each chapter will provide an introduction to handling various Cloud Operator administration tasks such as managing containers within your cloud; setting up/utilizing open source packages for monitoring; creating multiple users/tenants; taking instance snapshots; and customizing your cloud to run multiple active regions. Each chapter will also supply a step-by-step tutorial on how to automate these tasks with Ansible 2. 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 on the market today.
Table of Contents (17 chapters)
OpenStack Administration with Ansible 2 Second Edition
Credits
About the Author
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface

Chapter 9. Inventory Your Cloud

I am very excited to dive into this chapter, as we will focus on a topic that is considered challenging when administering an OpenStack cloud. Gathering metrics around the system being consumed is a pretty high item on the daily priority list. The bad news is OpenStack does not necessarily make this an easy task. In OpenStack's defense, I will say that there has been great work done around the most recent releases to improve this. The new OpenStackClient (OSC) has done a better job, allowing the Cloud Operator to pull together various different metrics about the cloud.

In the meantime, there are ways to collect these metrics in an ad hoc fashion and then put a very simple report together. As with most things related to OpenStack, there are a few ways to approach it. After attempting to do this using multiple methods, I found that it was easily accomplished by executing queries against the OpenStack databases. I know, I know...no one wants to touch the database...