Shilla Saebi 47ea20b8ea changed heat dev docs to comply with conventions

With the incorporation of many projects within OpenStack, it's very important to
use standards in the documentation This is important for formalization as well
as consistency
the proper usage is: heat or Orchestration or Orchestration module
heat should not be capitalized
https://wiki.openstack.org/wiki/Documentation/Conventions

Change-Id: Ia8d7f1429f877e4c88fc9b210948b63443376ba0

2015-04-24 22:03:07 -04:00

1.5 KiB

Raw Blame History

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 git@github.com:openstack/heat.git

Wiki: http://wiki.openstack.org/Heat
Developer docs: http://docs.openstack.org/developer/heat

Python client

https://github.com/openstack/python-heatclient

References

We have integration with

https://github.com/openstack/python-novaclient (instance)
https://github.com/openstack/python-keystoneclient (auth)
https://github.com/openstack/python-swiftclient (s3)
https://github.com/openstack/python-neutronclient (networking)
https://github.com/openstack/python-ceilometerclient (metering)
https://github.com/openstack/python-cinderclient (storage service)
https://github.com/openstack/python-glanceclient (image service)
https://github.com/openstack/python-troveclient (database as a Service)