OpenStack is a widely popular cloud-computing platform. Each of the OpenStack components that will be covered in subsequent chapters will be discussed in this preface. This will give you a high-level overview of these components and how they work together.
This book offers step-by-step practical instructions to help you quickly navigate through the complexities of OpenStack. While the examples in this book are situational, it can also be used as a reference for Linux-related topics and commands. This book provides you with the ability to reference both troubleshooting steps and specific commands for resolving complex issues.
Chapter 1, RDO Installation, presents a standard installation and an advanced installation of the RDO distribution of OpenStack. A demonstration architecture will be defined, and step-by-step instructions will be given.
Chapter 2, Identity Management, talks about Keystone, which is the identity-management component of OpenStack. You will be introduced to basic username-password authentication and the structure of how Keystone manages users, roles, tenants, and services.
Chapter 3, Image Management , talks about Glance, which is the image-management component. The process flow of how images are built, added to the registry, and consumed in the cluster will be presented.
Chapter 4, Network Management, talks about Neutron, which is the network-management component. Neutron can create and allocate virtual networks, routers, and IP addresses to OpenStack tenants. There is system preparation that is necessary for the cluster to allow external connectivity for instances.
Chapter 5, Instance Management, talks about Nova, which is the instance-management component. It is in charge of keeping track of which resources are used on which hypervisors, scheduling new instances for launch, and gathering all the resources necessary for an instance launch.
Chapter 6, Block Storage, talks about Cinder, which is the block storage-management component. It creates volumes and presents them to the instances. This can be done with multiple storage engines.
Chapter 7, Object Storage, talks about Swift, which is the object storage-management component. It creates object containers and manages file objects in the containers. Swift can optionally be backed with storage engines other than the default Swift object storage engine.
Chapter 8, Telemetry, talks about Ceilometer, which is the telemetry and metering component. It monitors the cluster and collects statistics of the resources that are in use.
Chapter 9, Orchestration, talks about Heat, which is the orchestration component. It is able to launch multiple instances and coordinate exchanging information about the instances within a heat stack.
Chapter 10, Docker, talks about containerization, which has become a prominent part of cloud computing. I'll go through the steps it takes to convert a compute node to a compute node that can support Docker containers.
Chapter 11, Scaling Horizontally, tells you how add a compute node and configure HAProxy by simply installing a new node, telling it where the control services are, and starting compute services.
Chapter 12, Monitoring, shows you how to use Nagios to perform basic monitoring.
Chapter 13, Troubleshooting, discusses some of the common issues that will surface while running an OpenStack cluster and where to go to find out where the error messages have been recorded.
While this book can be used by itself, you can benefit greatly by having a system with Red Hat Enterprise Linux available. The commands and resources discussed in this book are best learned when you have the ability to execute them on a test system. It is highly recommended you use Liberty software.
This book is perfect for administrators, cloud engineers, and operators who want to get started with OpenStack, solve basic problems encountered during deployment, and get up to speed with the latest release of OpenStack. Familiarity with the Linux command line and experience with Linux system administration is expected.
In this book, you will find a number of text styles that distinguish between different kinds of information. Here are some examples of these styles and an explanation of their meaning.
Code words in text, database table names, folder names, filenames, file extensions, pathnames, dummy URLs, user input, and Twitter handles are shown as follows: " In addition to the client package, you will also need the overcloudrc file from the undercloud."
A block of code is set as follows:
define service {
check_command check_nrpe!check_ovs_tunnel
host_name compute
service_description OVS tunnel connectivity
use generic-service
}Any command-line input or output is written as follows:
myhost# sudo ip addr add 192.0.2.222/24 dev bridget myhost# sudo ip link set up dev bridget
New terms and important words are shown in bold. Words that you see on the screen, for example, in menus or dialog boxes, appear in the text like this: "Click on Create User, and you're ready to start using the user's login and the new project."
Feedback from our readers is always welcome. Let us know what you think about this book—what you liked or disliked. Reader feedback is important for us as it helps us develop titles that you will really get the most out of.
To send us general feedback, simply e-mail <[email protected]>, and mention the book's title in the subject of your message.
If there is a topic that you have expertise in and you are interested in either writing or contributing to a book, see our author guide at www.packtpub.com/authors.
Now that you are the proud owner of a Packt book, we have a number of things to help you to get the most from your purchase.
Although we have taken every care to ensure the accuracy of our content, mistakes do happen. If you find a mistake in one of our books—maybe a mistake in the text or the code—we would be grateful if you could report this to us. By doing so, you can save other readers from frustration and help us improve subsequent versions of this book. If you find any errata, please report them by visiting http://www.packtpub.com/submit-errata, selecting your book, clicking on the Errata Submission Form link, and entering the details of your errata. Once your errata are verified, your submission will be accepted and the errata will be uploaded to our website or added to any list of existing errata under the Errata section of that title.
To view the previously submitted errata, go to https://www.packtpub.com/books/content/support and enter the name of the book in the search field. The required information will appear under the Errata section.
Piracy of copyrighted material on the Internet is an ongoing problem across all media. At Packt, we take the protection of our copyright and licenses very seriously. If you come across any illegal copies of our works in any form on the Internet, please provide us with the location address or website name immediately so that we can pursue a remedy.
Please contact us at <[email protected]> with a link to the suspected pirated material.
We appreciate your help in protecting our authors and our ability to bring you valuable content.
If you have a problem with any aspect of this book, you can contact us at <[email protected]>, and we will do our best to address the problem.