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 overview and roadmap

The following is the detailed overview of the functionality provided by Heat to the other components of OpenStack:

  • Heat uses templates: A text-based template file is used to describe the infrastructure of the cloud platform. This file is easily readable and can also be checked into version control.

  • Resources are defined in a template: These are the building blocks of the cloud platform which include servers, floating IP addresses, disk volumes, users, security groups, and other types.

  • Heat supports the autoscaling of servers and applications: The OpenStack Ceilometer component is used with Heat component to achieve autoscaling of virtual machine instances as well as applications running on top of them.

  • Heat templates include relationships between resource types: A relationship is specified between different types of resources inside a Heat template. Heat uses these relationships to associate them with each other. A typical example of this can be a disk volume attached...