openstack-manuals/doc/common/get-started-orchestration.rst
Emma Foley 388350ee08 [glossary] Remove acronyms [A-C]
- Remove acronym-only entries starting with [A-C].
- Consolodated duplicate entries.
- Resolve glossary references

Change-Id: I787e3129295e2acd7b3ecb1bbdd03b13ce4b5ca1
Implements: blueprint improve-glossary-usage
2016-08-22 14:33:24 +01:00

36 lines
1.4 KiB
ReStructuredText

==============================
Orchestration service overview
==============================
The Orchestration service 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 service
directly or through custom plug-ins.
The Orchestration service 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 :term:`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.