582b8b29cb
The format of the params received by the manager is a property of the Heat API protocol, not of the template, so it makes sense not to have the parser extracting the template parameter data from them. This simplifies the implementation of #123 (Nested Stacks). Change-Id: I8eaf50caf79f69359cbc8ee1f0193c08d7944d1c Signed-off-by: Zane Bitter <zbitter@redhat.com> |
||
---|---|---|
bin | ||
contrib | ||
docs | ||
etc | ||
heat | ||
templates | ||
tools | ||
.gitignore | ||
.gitreview | ||
HACKING.rst | ||
LICENSE | ||
MANIFEST.in | ||
README.rst | ||
babel.cfg | ||
install.sh | ||
openstack-common.conf | ||
pylintrc | ||
run_tests.sh | ||
setup.cfg | ||
setup.py | ||
tox.ini |
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
- http://docs.amazonwebservices.com/AWSCloudFormation/latest/APIReference/API_CreateStack.html
- http://docs.amazonwebservices.com/AWSCloudFormation/latest/UserGuide/create-stack.html
- http://docs.amazonwebservices.com/AWSCloudFormation/latest/UserGuide/aws-template-resource-type-ref.html
- http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=tosca
Related projects
- http://wiki.openstack.org/Donabe
- http://wiki.openstack.org/DatabaseAsAService (could be used to provide AWS::RDS::DBInstance)
- http://wiki.openstack.org/QueueService (could be used to provide AWS::SQS::Queue)