OpenStack Orchestration (Heat)
Go to file
Steven Hardy b2ab26398f heat API : Add support for ContentType=JSON query parameter
From reading the boto code, and looking at real AWS API responses
it would appear there is an (undocumented?) AWS query parameter
which switches response format from XML (default) to JSON
ref #125

Change-Id: I7c8b0f5701be5ff8bd0a3b135e42cf0e46e39ded
Signed-off-by: Steven Hardy <shardy@redhat.com>
2012-06-21 20:45:30 +01:00
bin Remove duplicate setup_logging() 2012-06-20 14:01:29 +10:00
contrib Add unit test framework nose and associated helper scripts 2012-04-13 17:10:30 -04:00
docs Add manpage for heat-metadata 2012-06-14 11:10:27 +02:00
etc Authentication Overhaul 2012-05-29 16:54:03 -07:00
heat heat API : Add support for ContentType=JSON query parameter 2012-06-21 20:45:30 +01:00
templates heat templates : Cleanup README and template whitespace 2012-06-21 14:05:37 +01:00
tools Lock to pep 1.1 2012-06-15 08:44:23 -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 Remove cfntools and jeos 2012-06-07 07:47:47 -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
install.sh Add install.sh 2012-06-08 12:54:03 +10: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 Lock to pep 1.1 2012-06-15 08:44:23 -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