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 event stack list

As explained earlier, events are associated with a stack. As explained in Chapter 3, Stack Group of Connected Cloud Resources, Heat uses the term "stack" to define a collection of resources combined together into a group for orchestration or scaling. These resources may include virtual machine (VM) instances, routers, switches, ports, router interfaces, security groups, subnets, storage volumes, and so on.

The command used to list events associated with a stack is as follows:

Ubuntu@ubunut $ heat event-list [-r <RESOURCE>] [-f <KEY1=VALUE1;KEY2=VALUE2...>]
                       [-l <LIMIT>] [-m <ID>]
                       <NAME or ID>




<NAME or ID>

This represents the name or ID of the stack for which events needed to be listed.

-r <RESOURCE>, --resource <RESOURCE>

This represents the name of resource for filtering the events.

-f <KEY1=VALUE1;KEY2=VALUE2...>, --filters <KEY1...