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

Setting up multi-tenant isolation


Using the breakdown provided in the previous section, we will now go step-by-step through each configuration, thus showing working configuration examples. The first part will be the pre-configuration steps required just to enable the multi-tenant isolation feature. After that we will then manually demonstrate the specific CLI commands to complete the configuration for a tenant.

Pre-configuration steps

Next, we will outline all the pre-configuration steps required before you can start your multi-tenant isolation setup.

Step 1

As mentioned earlier, probably the most important step is to add the additional Nova scheduler filters, in order to enable multi-tenant isolation. This is done by updating the nova.conf file, which is most likely located in the /etc/nova directory where the scheduler is installed. The filters to be added are named: AggregateInstanceExtraSpecsFilter and AggregateMultiTenancyIsolation. The following example is what it should look like once...