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

Coding the playbooks and roles


In this section, we will now create the playbook and roles to generate a comprehensive Cloud Report. Once the playbook is executed, the output and end result will be two reports consisting of the information we learned how to collect in the previous section. These two reports will be saved into a directory determined by you for retrieval. At that point, you can literally send it to leadership and/or peers for review. In the next chapter, we will learn how you can take things further and directly e-mail out the report as an added bonus.

Very similar to the previous chapter, we will break up the multiple tasks into separate roles to keep things organized. We will next review the six roles used to automate creating our Cloud Report.

cloud-inventory

The first role we will create will include those tasks needed to set up the foundation for the cloud report. The name of the file will be main.yml located within the role directory named cloud-inventory/tasks. The contents...