Over the past 6 years, hundreds of organizations have successfully implemented Infrastructure as a Service (IaaS) platforms based on OpenStack. The huge amount of investment from these organizations, industry giants, such as IBM, Cisco, Intel and HP, as well as open source leaders, such as Red Hat, Canonical, and SUSE, have 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.This guide 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 latest changes made in the latest OpenStack release and will also deal with advanced concepts, such as containerization, NVF, and security. At each point, we offer you advice based on the experience we'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, we focus on ensuring that your OpenStack project meets the needs of your organization, which will guarantee a successful rollout.
If you are a cloud architect who is responsible for designing and implementing private cloud with OpenStack, then this book is for you. System engineers and Enterprise architects will also find this book useful. Basic understanding of core OpenStack services as well as some working experience of concepts is recommended.
Chapter 1, Introduction to OpenStack, provides an overview of the OpenStack project. It covers the history, goals, governance, and components of the software. It also provides some examples of how the software has been used successfully in different industries to entice the reader to follow through the rest of the book. Finally, it provides the reader with an initial plan for architecting an OpenStack cloud.
Chapter 2, Architecting the Cloud, walks the reader through the initial set of choices that an organization makes when first designing their OpenStack cloud. Options are presented with guidance for software, hardware, network, and storage selection. In addition, physical site placement is discussed.
Chapter 3, Planning for Failure, covers design decisions that impact the scalability and availability of the cloud.
Chapter 4, Building the Deployment Pipeline, introduces the tenants of DevOps and translates them into a continuously integrated and delivered OpenStack deployment. The available configuration management system options for OpenStack are discussed, and the tools for driving automated builds are described.
Chapter 5, Building to Operate, covers day 2 management of OpenStack clouds and how architects can simplify operations through planning. Various tools and methods for monitoring, orchestration, and analytics are introduced.
Chapter 6, Integrating the Platform, describes the various integration strategies available for OpenStack clouds. Topics ranging from active directory integration to SOA Governance and API contracts are covered.
Chapter 7, Securing the Cloud, covers design considerations for the virtual environment inside of the OpenStack cloud.
Chapter 8, OpenStack Use Cases, walks the reader through some of the most popular use cases for OpenStack. Physical and virtual considerations for each use case and sample configurations are given.
Chapter 9, Containers, shows that the adoption of containers is dramatically changing the way we deploy and use OpenStack today. This chapter explores how to best use them to improve deployments.
Chapter 10, Conclusion, provides some forward-looking guidance on emerging technologies in the OpenStack space and how to integrate them into the deployment from earlier in the book.
All the software used in the examples in this book is available at no cost on the internet. Links are provided for each of the projects used. Many of the lab exercises require access to physical hardware or a virtualized environment for a lab. We recommend having at least 4 and up to 12 physical servers available for deploying OpenStack into production, depending on your requirements.
You can download the example code files for this book from your account at www.packtpub.com. If you purchased this book elsewhere, you can visit www.packtpub.com/support and register to have the files emailed directly to you.
You can download the code files by following these steps:
- Log in or register at www.packtpub.com.
- Select the
SUPPORTtab. - Click on
Code Downloads & Errata. - Enter the name of the book in the
Searchbox and follow the onscreen instructions.
Once the file is downloaded, please make sure that you unzip or extract the folder using the latest version of:
- WinRAR/7-Zip for Windows
- Zipeg/iZip/UnRarX for Mac
- 7-Zip/PeaZip for Linux
The code bundle for the book is also hosted on GitHub at https://github.com/PacktPublishing/OpenStack-for-Architects-Second-Edition. In case there's an update to the code, it will be updated on the existing GitHub repository.
We also have other code bundles from our rich catalog of books and videos available at https://github.com/PacktPublishing/. Check them out!
We also provide a PDF file that has color images of the screenshots/diagrams used in this book. You can download it from https://www.packtpub.com/sites/default/files/downloads/OpenStackforArchitectsSecondEdition_ColorImages.pdf.
There are a number of text conventions used throughout this book.
CodeInText: Indicates code words in text, database table names, folder names, filenames, file extensions, pathnames, dummy URLs, user input, and Twitter handles. Here is an example: "Copy the /etc/glance and /var/lib/glance directories."
A block of code is set as follows:
listen_tls = 1 listen_tcp = 0 auth_tls = "none"
Any command-line input or output is written as follows:
# packstack --allinoneBold: Indicates a new term, an important word, or words that you see onscreen. For example, words in menus or dialog boxes appear in the text like this. Here is an example: "Under Build, click on Add build step and select Execute shell."
Feedback from our readers is always welcome.
General feedback: Email [email protected] and mention the book title in the subject of your message. If you have questions about any aspect of this book, please email us at [email protected].
Errata: Although we have taken every care to ensure the accuracy of our content, mistakes do happen. If you have found a mistake in this book, we would be grateful if you would report this to us. Please visit www.packtpub.com/submit-errata, selecting your book, clicking on the Errata Submission Form link, and entering the details.
Piracy: If you come across any illegal copies of our works in any form on the Internet, we would be grateful if you would provide us with the location address or website name. Please contact us at [email protected] with a link to the material.
If you are interested in becoming an author: If there is a topic that you have expertise in and you are interested in either writing or contributing to a book, please visit authors.packtpub.com.
Please leave a review. Once you have read and used this book, why not leave a review on the site that you purchased it from? Potential readers can then see and use your unbiased opinion to make purchase decisions, we at Packt can understand what you think about our products, and our authors can see your feedback on their book. Thank you!
For more information about Packt, please visit packtpub.com.