The OpenStack Orchestration program aims to create a human and machine-accessible service that manages the entire life cycle of infrastructure and applications within OpenStack clouds. Heat is the cloud orchestration service for the OpenStack framework. It implements an orchestration engine to launch multiple composite cloud applications based on templates in the form of text files that can be treated like code. It is the most popular and a still-emerging IaaS cloud framework.
This book focuses on setting up and using one of the most important services in OpenStack Orchestration, Heat. First, the book introduces you to the orchestration service for OpenStack to help you understand the uses of the templating mechanism, complex control groups of cloud resources, and huge potential and multiple-use cases. It then moves on to the topology and orchestration specification for cloud applications and standards, before introducing the most popular IaaS cloud framework, Heat. You will get to grips with the standards used in Heat, an overview and a roadmap, the architecture and CLI, the Heat API, the Heat engine, the CloudWatch API, scaling principles, JeOS, and the installation and configuration of Heat. I'll wrap up by giving you some insights into troubleshooting for OpenStack.
With easy-to-follow, step-by-step instructions and supporting images, you will be able to manage OpenStack operations by implementing the orchestration services of Heat.
Chapter 1, Getting Started with the Orchestration Service for OpenStack, introduces OpenStack and provides an overview of OpenStack components.
Chapter 2, The OpenStack Architecture, focuses on the detailed architecture of OpenStack and its Heat components.
Chapter 3, Stack Group of Connected Cloud Resources, attempts to study the basics of Heat stacks and templates and discuss the autoscaling and high-availability mechanisms supported by Heat.
Chapter 4, Installation and Configuration of the Orchestration Service, installs the OpenStack Orchestration service, Heat. It will also show you how to write a simple template by creating a stack.
Chapter 5, Working with Heat, explores the architecture of Heat in further detail. It discusses the basic architecture of Heat and the main components that build up the Orchestration service for OpenStack. It also covers the command-line arguments accepted by Heat CLI. It explains the message flow for Heat. It also explores the architecture of Heat in further detail. It focuses on the following topics: the standards used in Heat, the Heat overview and roadmap, the Heat basics, architecture and CLI, the Heat basic workflow, the Heat API, the Heat engine, the Heat CloudWatch API, and Heat autoscaling principles.
Chapter 6, Managing Heat, covers the installation of DevStack with Heat support. We explore Heat functionality in detail. It also discusses the basic architecture of Heat and the main components that build up the Orchestration service for OpenStack. Then, it covers the command-line arguments accepted by Heat CLI.
Chapter 7, Troubleshooting Heat, focuses on troubleshooting the issues encountered when using Heat. It covers the most frequently occurring issues and discusses the possible solutions for them.
You will need OpenStack (Juno or Kilo). Also, you will need 1.2 Ghz CPU, 1 GB RAM, 40 GB HDD, and 2 X NIC cards. Finally, you will need Ubuntu 14.04 LTS.
If you are a system engineer, system administrator, cloud administrator, or a cloud engineer, then this book is for you. You should have a background of working in a Linux-based setup. Any knowledge of OpenStack-based cloud infrastructure will help you create wonders using this book.
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: "All available roles for trustor will be assigned to the trustee if no specific roles are mentioned in the heat.conf file."
A block of code is set as follows:
heat_template_version: 2013-05-23 description: Template that deploys single compute node. resources: my_compute-01: type: OS::Nova::Server properties: key_name: my_key image: F18-x86_64-cfntools flavor: m1.small
Any command-line input or output is written as follows:
keystone endpoint-create --service-id $(keystone service-list | awk '/ cloudformation / {print $2}' --public http://localhost:8000/v2/%\(tenant_id\)s --region regionOne
New terms and important words are shown in bold.
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.