Zane Bitter dea4bd18e0 Docs: Reorganise landing page
Consolidate into three sections based on the audience: operator, user, and
developer. Don't include API autodoc inline, just link to it.

Change-Id: I3c301d66dd05698fca3582761cb0177d66431483
2018-04-11 16:32:33 -04:00
2018-01-28 09:11:17 +05:30
2018-04-11 16:32:33 -04:00
2018-01-28 09:11:17 +05:30
2017-03-24 11:58:38 +08:00
2018-03-26 17:07:15 -04:00
2018-02-01 15:38:25 +00:00
2012-12-02 17:46:15 +00:00
2017-12-15 12:39:37 +05:30
2018-03-22 12:40:31 -04:00
2012-03-14 09:25:54 +11:00
2018-01-28 09:11:18 +05:30
2018-02-02 18:24:37 -06:00
2018-01-31 19:29:03 +00:00
2017-03-02 17:42:22 +00:00
2018-03-22 12:40:31 -04:00
2016-01-17 05:20:40 +00:00

Team and repository tags

image

Heat

Heat is a service to orchestrate multiple composite cloud applications using templates, through both an OpenStack-native REST API and a CloudFormation-compatible Query API.

Why heat? It makes the clouds rise and keeps them there.

Getting Started

If you'd like to run from the master branch, you can clone the git repo:

git clone https://git.openstack.org/openstack/heat

Python client

https://git.openstack.org/cgit/openstack/python-heatclient

References

We have integration with

Description
OpenStack Orchestration (Heat)
Readme 213 MiB
Languages
Python 99.5%
Shell 0.5%