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

Updating the design document


In this chapter, we've identified several different ways to interact with OpenStack using the available APIs. Now it is a good time to revisit the design document and fill out the Requirements section. An ideal set of requirements for an OpenStack cloud will have the following characteristics:

  • Each requirement should be atomic to limit the scope of the requirement
  • Each requirement should the contain context; there should be information on who will be using the functionality and under what circumstances
  • Each requirement should be testable, ideally in an automated fashion

If these conditions are met, we can generate policy documentation based on the principle that roles should have access to that functionality and we can generate automated test suites that verify that the requirements of the platform are met. These test suites can in turn be used in monitoring suites to ensure that the running system is performing according to specification.

Writing requirements

In this...