1b1dd456b21a32235ab0327f9fbc312892ec6c46
Adds a basic policy.json to authorize all actions for the CW API - this will deny access to the in-instance users defined in stack templates (which are assigned the heat_stack_user role) to all API actions apart from PutMetricData action, which is used by cfn-push-stats to provide metric data from the instances Change-Id: I2bbb885bec98b85828cdb92d7efc0688da7be3c1 Signed-off-by: Steven Hardy <shardy@redhat.com>
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 GettingStarted: http://wiki.openstack.org/Heat/GettingStartedUsingDevstack
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
We have integration with
Description
Languages
Python
99.5%
Shell
0.5%