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.

Related Content you might be interested in

Current Title:

Small book image
OpenStack Orchestration
Adnan Ahmed Siddiqui
Oct, 2015 | 150 pages
No titles found
Table of Contents (14 chapters)
OpenStack Orchestration
OpenStack Orchestration
Credits
Credits
About the Author
About the Author
About the Reviewers
About the Reviewers
www.PacktPub.com
www.PacktPub.com
Preface
Preface
Free Chapter
1
Getting Started with the Orchestration Service for OpenStack
Getting Started with the Orchestration Service for OpenStack
Introduction to the OpenStack architecture
The Orchestration service for OpenStack
The Heat workflow
The Orchestration authorization model
The authorization model configuration
Stack domain users
Summary
2
The OpenStack Architecture
The OpenStack Architecture
Components of OpenStack
OpenStack node types
The OpenStack logical architecture
TOSCA – Heat ideas and standards
Heat components
The example architecture 1 (based on the Nova network)
The example architecture 2 (based on Neutron)
Network layout for OpenStack networking
Summary
3
Stack Group of Connected Cloud Resources
Stack Group of Connected Cloud Resources
Heat basics
Autoscaling
Summary
4
Installation and Configuration of the Orchestration Service
Installation and Configuration of the Orchestration Service
Orchestration module concepts
OpenStack Heat installation
Creating a stack with Heat
Summary
5
Working with Heat
Working with Heat
Standards used in Heat
Heat overview and roadmap
The Heat architecture and CLI
The Heat basic workflow
JeOS
Summary
6
Managing Heat
Managing Heat
Heat and DevStack
The event stack list
Get the stack list
Create a stack
Show stack details
Show resource details
Update a stack
Delete a stack
The template structure
The CloudFormation template
Summary
7
Troubleshooting Heat
Troubleshooting Heat
VM instances cannot connect to the external network or the Internet
Error received during installation – Unable to write random state
Timeout error received while running jeos_create during customization
A template running with incorrect parameters cannot be deleted
Error – internal error process exited while connecting to monitor
It takes too long to create a JeOS
Error – Quota exceeded: code=InstanceLimitExceeded (HTTP 413)
Error – Response from Keystone does not contain a Heat endpoint
Error – Internal Server Error
Error – Provided KeyName is not registered with Nova
A template is not working after editing
Instances shutdown immediately after creation
Yum update fails with dependency problems related to the oz package
Failed to start qpidd
OpenStack daemons can't connect to qpidd
Ubuntu VMs cannot receive DHCP assignments from hosts running CentOS/Fedora
Debugging OpenStack Heat
Heat list returns 503 error
Heat list hangs up
Troubleshooting common OpenStack errors
Summary
Index
Index

Heat and DevStack

DevStack provides a set of scripts for automated installation of OpenStack on Ubuntu as well as Fedora Linux. It is a tool to help OpenStack developers to quickly set up an OpenStack environment using scripts. These scripts automatically download or clone the required packages and repositories from the OpenStack website that are necessary for setting up an OpenStack cloud.

One drawback with this approach is that the environment is not persistent across server reboots. There are scripts such as rejoin-stack that need to be run to recreate the environment after a server has been rebooted.

Therefore, DevStack is not recommended for a production install. However, it can only be used for testing and development purpose, where an OpenStack environment is created and destroyed several times. When OpenStack is required in a purely development environment, other methods of installation can be used.

DevStack can also be configured for enabling and using Heat services. This can be done...

Previous Section
End of Section 2
Next Section