Chapter 9. OpenStack Orchestration Installation
- 9.1. Orchestration Service Overview
- 9.2. Install the Orchestration Service Packages
- 9.3. Configure the Orchestration Service
- 9.3.1. Configure the Orchestration Service Database Connection
- 9.3.2. Restrict the Bind Addresses of each Orchestration API Service
- 9.3.3. Create the Orchestration Service Identity Records
- 9.3.4. Configure Orchestration Service Authentication
- 9.3.5. Configure RabbitMQ Message Broker Settings for the Orchestration Service
- 9.4. Launch the Orchestration Service
- 9.5. Deploy a Stack Using Orchestration Templates
- 9.6. Integrate Telemetry and Orchestration Services
9.1. Orchestration Service Overview
The Orchestration service provides a template-based way to create and manage cloud resources such as storage, networking, instances, or applications.
Templates are used to create stacks, which are collections of resources (for example instances, floating IPs, volumes, security groups, or users). The service offers access to all OpenStack core services using a single modular template, with additional orchestration capabilities such as auto-scaling and basic high availability.
Features include:
- A single template provides access to all underlying service APIs.
- Templates are modular (resource oriented).
- Templates can be recursively defined, and therefore reusable (nested stacks). This means that the cloud infrastructure can be defined and reused in a modular way.
- Resource implementation is pluggable, which allows for custom resources.
- Autoscaling functionality (automatically adding or removing resources depending upon usage).
- Basic high availability functionality.
Table 9.1. Orchestration service components
| Component | Description |
|---|---|
|
heat
|
A CLI tool that communicates with the heat-api to execute AWS CloudFormation APIs.
|
|
heat-api
|
An OpenStack-native REST API that processes API requests by sending them to the heat-engine over RPC.
|
|
heat-api-cfn
|
Provides an AWS-Query API that is compatible with AWS CloudFormation and processes API requests by sending them to the heat-engine over RPC.
|
|
heat-engine
|
Orchestrates the launching of templates and provide events back to the API consumer.
|
|
heat-api-cloudwatch
|
Provides monitoring (metrics collection) for the Orchestration service.
|
|
heat-cfntools
|
A package of helper scripts (for example, cfn-hup, which handles updates to metadata and executes custom hooks).
|
Note
The
heat-cfntools package is only installed on images that are launched by heat into Compute servers.