OpenStack Orchestration (Heat)
Go to file
Zane Bitter 8550a36f48 Delete networks when erasing OpenStack
This is required to remove any network interfaces created using nova. If
these are left behind they prevent a new installation of OpenStack
re-adding them.

Signed-off-by: Zane Bitter <zbitter@redhat.com>
2012-05-18 22:42:37 +02: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 api : fix pep8 warning 2012-05-17 21:43:51 +01:00
templates Slim down the getting_started template. 2012-05-14 21:15:23 +10:00
tools Delete networks when erasing OpenStack 2012-05-18 22:42:37 +02:00
var Adding the metadata.log file 2012-04-30 10:13:15 -04:00
.gitignore Copied the python-novaclient test code to avoid importing via python path 2012-04-30 10:39:51 -04: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 Add cfn-get-metadata to the manifest 2012-05-11 18:56:12 +02: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 openstack-common: timeutils and importutils seperated out 2012-04-27 10:23:19 +10: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 Add setup.py and friends 2012-03-14 09:25:54 +11:00
setup.py Add skeleton structure for the metadata server 2012-04-27 18:40:49 +02:00
tox.ini Add ability to automate testing with tox. 2012-05-08 17:39:08 -04: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