2e7e7c44cf
The user which authenticates keystone tokens should be the "heat" user in the "service" tenant. This changes the default configuration to do this, as devstack already does. Ref #269 Change-Id: I89978ec0b490f6d404c568197dd4208097a4b695 Signed-off-by: Zane Bitter <zbitter@redhat.com>
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)