805a73b1e7
contrib/ directory does not follow any standards and will make it harder to programmatically install plugins on devstack. The current structure can also cause namespace collisions when loading them. This moves all plugin modules to a folder with the same name under their directory (e.g. contrib/rackspace/rackspace), allowing requirements, readmes, and other files to be separate from the actual code. This also helps to avoid namespace collisions when loading all the plugins, since all plugins will be under their namespace in the heat package. Example: heat.engine.plugins heat.engine.plugins.docker heat.engine.plugins.marconi heat.engine.plugins.rackspace Since plugin packages are now in a folder one level under contrib/, testr.conf is also updated so that all plugins are discovered correctly. Co-Authored-By: Anderson Mesquita <andersonvom@gmail.com> Related-Bug: #1271226 Change-Id: Ifc8e3ca388253be82471651737da5d399c7cfb98
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