openstack-manuals/doc/common-rst/get_started_orchestration.rst
daz c6036a4c8e Convert Cloud Admin Guide files to RST
Files converted:
- common/ch_getstart.xml
- common/section_getstart_compute.xml
- common/section_storage-concepts.xml
- common/section_getstart_object-storage.xml
- common/section_getstart_block-storage.xml
- common/section_getstart_networking.xml
- common/section_getstart_dashboard.xml
- common/section_keystone-concepts.xml
- common/section_getstart_image.xml
- common/section_getstart_telemetry.xml
- common/section_getstart_orchestration.xml
- common/section_getstart_trove.xml
- common/section_getstart_sahara.xml
- common/section_getstart_conceptual_arch.xml
- common/section_getstart_logical_arch.xml

Change-Id: I41318a887af6855f3a25e6adedbbd9e75f431332
Implements: blueprint reorganise-user-guides
2015-07-13 10:27:29 +10:00

1.4 KiB

Orchestration module concepts

The Orchestration module provides a template-based orchestration for describing a cloud application, by running OpenStack API calls to generate running cloud applications. The software integrates other core components of OpenStack into a one-file template system. The templates allow you to create most OpenStack resource types, such as instances, floating IPs, volumes, security groups and users. It also provides advanced functionality, such as instance high availability, instance auto-scaling, and nested stacks. This enables OpenStack core projects to receive a larger user base.

The service enables deployers to integrate with the Orchestration module directly or through custom plug-ins.

The Orchestration module consists of the following components:

heat command-line client

A CLI that communicates with the heat-api to run AWS CloudFormation APIs. End developers can directly use the Orchestration REST API.

heat-api component

An OpenStack-native REST API that processes API requests by sending them to the heat-engine over Remote Procedure Call (RPC).

heat-api-cfn component

An AWS Query API that is compatible with AWS CloudFormation. It processes API requests by sending them to the heat-engine over RPC.

heat-engine

Orchestrates the launching of templates and provides events back to the API consumer.