Book Image

OpenStack Orchestration

By : Adnan Ahmed Siddiqui
Book Image

OpenStack Orchestration

By: Adnan Ahmed Siddiqui

Overview of this book

This book is focused 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. We then move 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, overview and roadmap, architecture and CLI, heat API, heat engine, CloudWatch API, scaling principles, JeOS and installation and configuration of Heat. We 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.
Table of Contents (14 chapters)
OpenStack Orchestration
About the Author
About the Reviewers
Stack Group of Connected Cloud Resources

Heat basics

Heat is a major project of OpenStack that is focused on orchestration and autoscaling. It allows deployment of complex cloud applications by defining them in text files, which it calls templates. The Heat engine parses and processes these templates. Heat understands the template format used by AWS CloudFormation, while there is a native Heat template format called HOT. The compatibility with AWS CloudFormation template system makes it possible to use several existing the AWS CloudFormation templates to be used with OpenStack.

A great advantage of orchestration is the ability of treating hardware infrastructure as code and providing features for autoscalability.

The source code for infrastructure can also be checked into version control as it can be done for software programs. Use of the YAML markup for templates makes this easy; therefore, HOT templates use YAML instead of JSON.

There are two types of APIs currently being supported by Heat; they are:

  • The OpenStack native REST API...