blob: ac06056528e4b4b8fd5a4b30dc1d4dc3e0c86dd1 [file] [log] [blame]
Filip Pytloun923d8692015-10-06 16:28:32 +02001
2====
3Heat
4====
5
Jakub Pavlik3bed97a2016-05-20 11:16:08 +02006Heat is the main project in the OpenStack Orchestration program. It implements
7an orchestration engine to launch multiple composite cloud applications based
8on templates in the form of text files that can be treated like code. A native
9Heat template format is evolving, but Heat also endeavours to provide
10compatibility with the AWS CloudFormation template format, so that many
11existing CloudFormation templates can be launched on OpenStack. Heat provides
12both an OpenStack-native ReST API and a CloudFormation-compatible Query API.
Filip Pytloun923d8692015-10-06 16:28:32 +020013
14Sample pillars
15==============
16
17Single Heat services on the controller node
18
19.. code-block:: yaml
20
21 heat:
22 server:
23 enabled: true
24 version: icehouse
Jakub Pavlik51e15e02016-03-12 13:32:26 +010025 region: RegionOne
Filip Pytloun923d8692015-10-06 16:28:32 +020026 bind:
27 metadata:
28 address: 10.0.106.10
29 port: 8000
30 waitcondition:
31 address: 10.0.106.10
32 port: 8000
33 watch:
34 address: 10.0.106.10
35 port: 8003
36 cloudwatch:
37 host: 10.0.106.20
38 api:
39 host: 10.0.106.20
40 api_cfn:
41 host: 10.0.106.20
42 database:
43 engine: mysql
44 host: 10.0.106.20
45 port: 3306
46 name: heat
47 user: heat
48 password: password
49 identity:
50 engine: keystone
51 host: 10.0.106.20
52 port: 35357
53 tenant: service
54 user: heat
55 password: password
Dennis Dmitriev09650272017-03-09 17:51:00 +020056 endpoint_type_default: internalURL
57 endpoint_type_heat: publicURL
Filip Pytloun923d8692015-10-06 16:28:32 +020058 message_queue:
59 engine: rabbitmq
60 host: 10.0.106.20
61 port: 5672
62 user: openstack
63 password: password
64 virtual_host: '/openstack'
65 ha_queues: True
66
67Heat client with specified git templates
68
69.. code-block:: yaml
70
71 heat:
72 client:
73 enabled: true
Jiri Broulikb2ef3282017-02-07 22:33:30 +010074 template:
75 admin:
76 domain: default
77 source:
78 engine: git
79 address: git@repo.domain.com/admin-templates.git
80 revision: master
81 default:
82 domain: default
83 source:
84 engine: git
85 address: git@repo.domain.com/default-templates.git
86 revision: master
87
Filip Pytloun923d8692015-10-06 16:28:32 +020088
89Heat system definition of several stacks/systems
90
91.. code-block:: yaml
92
93 heat:
94 control:
95 enabled: true
96 system:
97 web_production:
98 format: hot
99 template_file: /srv/heat/template/web_cluster.hot
100 environment: /srv/heat/env/web_cluster/prd.env
101 web_staging:
102 format: hot
103 template_file: /srv/heat/template/web_cluster.hot
104 environment: /srv/heat/env/web_cluster/stg.env
105
106Ceilometer notification
107
108.. code-block:: yaml
109
110 heat:
111 server:
112 enabled: true
113 version: icehouse
114 notification: true
115
Jiri Konecnyf94dd922016-04-20 12:09:22 +0200116
117Client-side RabbitMQ HA setup
118
119.. code-block:: yaml
120
121 heat:
122 server:
123 ....
124 message_queue:
125 engine: rabbitmq
126 members:
127 - host: 10.0.16.1
128 - host: 10.0.16.2
129 - host: 10.0.16.3
130 user: openstack
131 password: pwd
132 virtual_host: '/openstack'
133 ....
134
135
136
Filip Pytloun923d8692015-10-06 16:28:32 +0200137Usage
138=====
139
140Install Contrail Heat plugin for additional resources
141
142.. code-block:: bash
143
144 pip install git+https://github.com/Juniper/contrail-heat.git@R1.30
145
Filip Pytloun923d8692015-10-06 16:28:32 +0200146Things to improve
147=================
148
149* IBM UrbanCode Deploy - has resources for AWS and VMWare
150 http://www.ibm.com/developerworks/rational/library/multi-platform-application-deployment-urbancode-deploy/
151
Jakub Pavlik3bed97a2016-05-20 11:16:08 +0200152Documentation and Bugs
153============================
154
155To learn how to deploy OpenStack Salt, consult the documentation available
156online at:
157
158 https://wiki.openstack.org/wiki/OpenStackSalt
159
160In the unfortunate event that bugs are discovered, they should be reported to
161the appropriate bug tracker. If you obtained the software from a 3rd party
162operating system vendor, it is often wise to use their own bug tracker for
163reporting problems. In all other cases use the master OpenStack bug tracker,
164available at:
165
166 http://bugs.launchpad.net/openstack-salt
167
168Developers wishing to work on the OpenStack Salt project should always base
169their work on the latest formulas code, available from the master GIT
170repository at:
171
172 https://git.openstack.org/cgit/openstack/salt-formula-heat
173
174Developers should also join the discussion on the IRC list, at:
175
Filip Pytloundc94d872017-02-02 13:02:03 +0100176 https://wiki.openstack.org/wiki/Meetings/openstack-salt
177Documentation and Bugs
178======================
179
180To learn how to install and update salt-formulas, consult the documentation
181available online at:
182
183 http://salt-formulas.readthedocs.io/
184
185In the unfortunate event that bugs are discovered, they should be reported to
186the appropriate issue tracker. Use Github issue tracker for specific salt
187formula:
188
189 https://github.com/salt-formulas/salt-formula-heat/issues
190
191For feature requests, bug reports or blueprints affecting entire ecosystem,
192use Launchpad salt-formulas project:
193
194 https://launchpad.net/salt-formulas
195
196You can also join salt-formulas-users team and subscribe to mailing list:
197
198 https://launchpad.net/~salt-formulas-users
199
200Developers wishing to work on the salt-formulas projects should always base
201their work on master branch and submit pull request against specific formula.
202
203 https://github.com/salt-formulas/salt-formula-heat
204
205Any questions or feedback is always welcome so feel free to join our IRC
206channel:
207
208 #salt-formulas @ irc.freenode.net