29807237cb
The Heat API doesn't behave properly if it is behind an SSL termination proxy. If this is the case, the HTTP redirections and the links returned in the REST response bodies are build using http protocol instead of https. To handle this situation, a new middleware was added. The purpose of the SSLMiddleware is to update the wsgi.url_scheme environment variable of the request with the value contained in an HTTP header that can be configured in heat.conf (by default: 'X-Forwarded-Proto') Change-Id: I418cd8cf2fb2a5fb3f630b4945084fb6eab57310 Closes-Bug: #1235555
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