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

The Heat architecture and CLI

The Heat project of OpenStack consists of several components, which interact with each other to provide the Orchestration service.

The following diagram depicts the high-level architecture of Heat components for OpenStack:

The Heat architecture

We will repeat the same table from Chapter 4, Installation and Configuration of the Orchestration Service, which includes the important components of Heat:





The command-line client

There is a command-line interface that interacts with the Heat API and runs Orchestration commands using the AWS CloudFormation API.



This is an OpenStack-native REST API that processes API requests using RPC to the heat-engine.



This is a query API compatible with AWS CloudFormation. It is responsible for processing API requests by sending them to heat-engine over RPC.



This is the core engine that orchestrates launching of templates and sends events...