Book Image

OpenStack for Architects - Second Edition

By : Michael Solberg, Ben Silverman
Book Image

OpenStack for Architects - Second Edition

By: Michael Solberg, Ben Silverman

Overview of this book

Over the past six years, hundreds of organizations have successfully implemented Infrastructure as a Service (IaaS) platforms based on OpenStack. The huge amount of investment from these organizations, including industry giants such as IBM and HP, as well as open source leaders, such as Red Hat, Canonical, and SUSE, has led analysts to label OpenStack as the most important open source technology since the Linux operating system. Due to its ambitious scope, OpenStack is a complex and fast-evolving open source project that requires a diverse skill set to design and implement it. OpenStack for Architects leads you through the major decision points that you'll face while architecting an OpenStack private cloud for your organization. This book will address the recent changes made in the latest OpenStack release i.e Queens, and will also deal with advanced concepts such as containerization, NVF, and security. At each point, the authors offer you advice based on the experience they've gained from designing and leading successful OpenStack projects in a wide range of industries. Each chapter also includes lab material that gives you a chance to install and configure the technologies used to build production-quality OpenStack clouds. Most importantly, the book focuses on ensuring that your OpenStack project meets the needs of your organization, which will guarantee a successful rollout.
Table of Contents (17 chapters)
Title Page
Copyright and Credits
Packt Upsell
Contributors
Preface
Index

OpenStack On Containers


We've talked about containers on OpenStack, but as OpenStack evolves, more motion is being directed to running OpenStack on containers. Today, the most common architecture for OpenStack clouds consists of one or more bare metal servers that house the control services in order to operate OpenStack. When configured for high availability, these bare metal servers can scale horizontally, but for the most part, they will contain the exact same control plane services on each server. We call this a monolithic control plane design. The limitations of this design are mostly centered around scaling the services, both stateful and stateless. Although most of OpenStack's stateless servers can scale horizontally very wide, there are some issues with the stateful services and the way they are load balanced. This presents limitations to horizontal scaling; for example, when scaling corosync, you are limited to 16 cluster members, in some cases more, but none have been well tested...