b8eefd1de9fa9617571756566ab8facd2220bba0
When the the instance_user value from heat.conf is set to empty string/None and the user doesn't specify Server's admin_user property, Heat will not create a custom cloud-init user. The instance_user config option and admin_user property are deprecated and will be removed in Juno where this behaviour becomes the default. AWS::EC2::Instance will still create a cloud-init user for CloudFormation compatibility. In the absence of the instance_user config option, 'ec2-user' will be used. Closes-Bug: #1257410 Change-Id: I42dda36045f79be079b2030669284e9db71463d7
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
We have integration with
Description
Languages
Python
99.5%
Shell
0.5%