Show Table of Contents
9.4. Deploy a Stack Using Orchestration Templates
The Orchestration engine service uses templates (defined as
.templatefiles) to launch instances, IPs, volumes, or other types of stacks. The heat utility is a command-line interface that allows you to create, configure, and launch stacks.
The openstack-heat-templates package provides sample templates that you can use to test core Orchestration features. It also contains template-related scripts and conversion tools. To install this package, run the following command:
yum install -y openstack-heat-templates
Some Orchestration templates launch instances that require access to the
openstack-heat-api-cfnservice. Such instances must be able to communicate with the
openstack-heat-api-cloudwatchservice and the
openstack-heat-api-cfnservice. The IPs and ports used by these services are the values set in the
To allow access to these services, you must open the ports used by
Procedure 9.8. Deploying a Stack Using Orchestration Templates
- Open the
/etc/sysconfig/iptablesfile in a text editor.
- Add the following INPUT rules to allow TCP traffic on ports
-A INPUT -i BR -p tcp --dport 8003 -j ACCEPT -A INPUT -i BR -p tcp --dport 8000 -j ACCEPT -A INPUT -p tcp -m multiport --dports 8004 -j ACCEPTReplace BR with the interface of the bridge used by the instances launched from Orchestration templates. Do not include the
-i BRparameter in the
INPUTrules if you are not using
nova-network, or if the Orchestration service and
nova-computeare not hosted on the same server.
- Save the changes to the
- Restart the
iptablesservice for the firewall changes to take effect:
systemctl restart iptables.service
- Launch an application:
heat stack-create STACKNAME \
--parameters="PARAMETERS"Replace the following values:
- Replace STACKNAME with the name to assign to the stack. This name will appear when you run the
- Replace PATH_TEMPLATE with the path to your
- Replace PARAMETERS with a semicolon-delimited list of stack creation parameters to use. Supported parameters are defined in the template file itself.