419a3d953e
keystone auth_token middleware now allows heat to have auth_token configuration in heat-api.conf. Moves the example of auth_token configuration from heat-api-paste.ini to heat-api.conf. This simplifies user configuations and users is no longer required to edit heat-api-paste.ini. This does not break backward compatibility. auth_token first tries the configurations in /etc/heat/heat-api-paste.ini and then the above configurations. Thus a user who already uses heat-api-paste.ini does not need to change it. Change-Id: Ia0a4d912cd7380094e121ee4af733277ca4d812e Blueprint: keystone-middleware
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
- Wiki: http://wiki.openstack.org/Heat
- Developer docs: http://docs.openstack.org/developer/heat
Python client
https://github.com/openstack/python-heatclient
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