Book Image

Production Ready OpenStack - Recipes for Successful Environments

By : Arthur Berezin
Book Image

Production Ready OpenStack - Recipes for Successful Environments

By: Arthur Berezin

Overview of this book

OpenStack is the most popular open source cloud platform used by organizations building internal private clouds and by public cloud providers. OpenStack is designed in a fully distributed architecture to provide Infrastructure as a Service, allowing us to maintain a massively scalable cloud infrastructure. OpenStack is developed by a vibrant community of open source developers who come from the largest software companies in the world. The book provides a comprehensive and practical guide to the multiple uses cases and configurations that OpenStack supports. This book simplifies the learning process by guiding you through how to install OpenStack in a single controller configuration. The book goes deeper into deploying OpenStack in a highly available configuration. You'll then configure Keystone Identity Services using LDAP, Active Directory, or the MySQL identity provider and configure a caching layer and SSL. After that, you will configure storage back-end providers for Glance and Cinder, which will include Ceph, NFS, Swift, and local storage. Then you will configure the Neutron networking service with provider network VLANs, and tenant network VXLAN and GRE. Also, you will configure Nova's Hypervisor with KVM, and QEMU emulation, and you will configure Nova's scheduler filters and weights. Finally, you will configure Horizon to use Apache HTTPD and SSL, and you will customize the dashboard's appearance.
Table of Contents (16 chapters)
Production Ready OpenStack - Recipes for Successful Environments
About the Author
About the Reviewers

Configuring Cinder with multiple backends

Previous parts of this chapter discussed configuring various backend storage drivers with the cinder-volume service. Cinder allows configuring and utilizing multiple storage backends simultaneously. While configuring multiple storage backends with Cinder, a cinder-volume process is launched for each storage backend. We can choose a name for each storage backend that can be specified while creating new Cinder volumes. Cinder also supports setting identical names for several storage backends. In this scenario, Cinder-Scheduler decides where to place new volumes when created, based on weighing of the scheduler. This will be discussed further in the next section.

Getting ready

In this section, we will configure cinder to use two separate LVM volume groups as storage backends. Under the default section, we will specify two storage provider names separated by commas, and we will configure each of the storage providers and name them.

How to do it…

Follow these...