Go to file
Clint Byrum a60f6d4569 Do not initialize anything during import phase
The structure of the program is compromised by doing too much logic in
the import phase. We can read the code more cleanly if we can see where
the intended initialization code is called. This may make tests slightly
more tedious to write, but that should be handled by writing generic
fixtures which can be reused for exactly this purpose.

Change-Id: I1d221e2f90d1f6e89717a37d2128caabd077d30a
2013-04-24 10:03:06 -07:00
2013-03-12 10:03:37 +01:00
2013-04-11 22:37:04 -07:00
2013-03-20 14:21:08 -04:00
2012-12-02 17:46:15 +00:00
2012-03-14 09:25:54 +11:00
2013-03-20 14:21:08 -04:00
2013-02-18 17:27:14 +00:00
2013-03-19 14:54:35 -07:00
2012-06-23 22:41:30 -04:00

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

Python client

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

References

We have integration with

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