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
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
3
Stack Group of Connected Cloud Resources
Index

OpenStack Heat installation


In this section, we will describe the steps for installing Heat on Ubuntu Linux:

  1. Change to the super user mode:

  2. Install Heat packages:

  3. Create a MySQL database for Heat:

    The default connection string to sqlite_db needs to be replaced with a new string to the MySQL database. The HEAT_DBPASS parameter needs to be replaced with the actual password for the heat database:

  4. Configure the service user and role:

  5. Register the service and create the endpoint:

  6. Create the heat_stack_user role:

  7. Install the OpenStack client:

  8. Create the heat_stack_owner role and give role to users (admin and demo) who create Heat stacks:

  9. Edit the /etc/heat/heat.conf file:

  10. Replace the connection string, as shown in the following screenshot:

    After incorporating the changes, the configuration file heat.conf should look like the following screenshot:

    It is also important to mention the heat instance user in the same configuration file under the [DEFAULT] section. user_instance is required to access VM via SSH...