OpenStack Orchestration (Heat)
Go to file
Steven Dake 72c383396d Only run cfn-init once
cloud-config-final.service (atleast in Fedora 16) runs the user scripts.  So
there is no need to run them in cloud-config.service (which this file is processed
by).

May need a revisit on deb based systems.

Change-Id: Ib7c3d56a50bcdc4ea68626e1d57a28a4ec70e1b4
Signed-off-by: Steven Dake <sdake@redhat.com>
2012-05-23 07:42:19 -07:00
bin Allow engine and metadata server start in any order 2012-05-17 16:49:15 +02:00
contrib Add unit test framework nose and associated helper scripts 2012-04-13 17:10:30 -04:00
docs Wait for instance startup in GettingStarted test 2012-05-18 14:02:38 +02:00
etc heat cli : Add options to bash completion script 2012-05-16 09:48:37 +01:00
heat Only run cfn-init once 2012-05-23 07:42:19 -07:00
templates Merge branch 'puppet_instances' 2012-05-21 15:39:11 -04:00
tools tools/openstack: Updated to latest openstack F16/F17 tools 2012-05-22 09:51:24 -07:00
.gitignore Align with project standards. 2012-05-21 16:48:34 -07:00
.gitreview Update gitreview for new Stackforge remote 2012-05-22 13:11:39 +01:00
HACKING.rst Directives to not use variable names that conflict with pdb 2012-03-20 07:16:16 -04:00
LICENSE Initial commit (basics copied from glance) 2012-03-13 21:48:07 +11:00
MANIFEST.in Align with project standards. 2012-05-21 16:48:34 -07:00
README.rst renaming CloudFormations to CloudFormation 2012-04-13 15:01:41 -04:00
babel.cfg Add setup.py and friends 2012-03-14 09:25:54 +11:00
openstack-common.conf Align with project standards. 2012-05-21 16:48:34 -07:00
pylintrc Directives to not use variable names that conflict with pdb 2012-03-20 07:16:16 -04:00
run_tests.sh Add option to exclude pep8 examination to run_test.sh. 2012-05-08 14:41:21 -04:00
setup.cfg Align with project standards. 2012-05-21 16:48:34 -07:00
setup.py Align with project standards. 2012-05-21 16:48:34 -07:00
tox.ini Align with project standards. 2012-05-21 16:48:34 -07:00

README.rst

HEAT

This is an OpenStack style project that provides a REST API to orchestrate multiple cloud applications implementing well-known standards such as AWS CloudFormation and TOSCA.

Currently the developers are focusing on AWS CloudFormation but are watching the development of the TOSCA specification.

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:heat-api/heat.git

Follow the steps: https://github.com/heat-api/heat/wiki/HeatGettingStarted

References