OpenStack Orchestration (Heat)
3a1e7838ff
Use a rule in the policy.json to correctly derive a user's admin-ness based on their roles, when it is not explicitly specified in the RequestContext constructor. Keystone auth_token tests X-Roles based on the user role membership for the tenant the token is scoped to, so this will allow us to define per-tenant admins (the admin everywhere issue described in keystone bug #968696 won't apply here, that is specific to keystone). Remove the admin_role config option, which doensn't do anything, and now this should be specified via policy.json. Change-Id: I1921a2b515ecc8ca5d37205e3cdb6b7b8695b1ac bluprint: request-scoping-policy |
||
---|---|---|
bin | ||
contrib/rackspace | ||
doc | ||
etc/heat | ||
heat | ||
tools | ||
.gitignore | ||
.gitreview | ||
.testr.conf | ||
babel.cfg | ||
CONTRIBUTING.rst | ||
HACKING.rst | ||
install.sh | ||
LICENSE | ||
MANIFEST.in | ||
openstack-common.conf | ||
pylintrc | ||
README.rst | ||
requirements.txt | ||
run_tests.sh | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini | ||
uninstall.sh |
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