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

Monitoring the cloud


If allowed I would like to cover some monitoring basics before getting started here. Hopefully, the three principles I will share here are not new to you. When evaluating to monitor something, there are three base principles to keep in mind:

  • Keep it simple

  • Keep your monitoring close to your infrastructure

  • Create good monitors

The first point is pretty easy to absorb, as it is rather self-explanatory. The worst thing you could ever do is over complicate something as important as monitoring. This principle not only applies to your overall approach, but it also applies to the tool you choose to do the monitoring. If you have to create a Visio diagram of your monitoring platform, it is too complicated.

The next point of keeping your monitoring close to your infrastructure is meant to express that the tool used to monitor should physically reside close to the infrastructure/application. The monitoring platform should not have to traverse VPNs or multiple firewalls just to poll...