Heat is made up of three daemons:
- heat-api: The API and primary gateway to Heat. One must interact with heat-api to create, list, delete, and manage stacks.
- heat-api-cfn: This provides an AWS-style Query API that allows services or human users to utilize CloudFormation-like functionalities, such as wait conditions and triggering autoscaling.
- heat-engine: This is responsible for launching stacks and managing all resources specified in the template.
Figure 9.1: High-level view of Heat architecture
