Go to file
Tomas Sedovic b8eefd1de9 Don't create cloud-init user unless specified
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
2014-03-25 05:01:11 -04:00
2014-03-04 08:51:56 -06:00
2014-03-13 14:37:22 -05:00
2014-01-25 13:58:21 +08:00
2012-12-02 17:46:15 +00:00
2014-03-03 10:49:28 -05:00
2012-03-14 09:25:54 +11:00
2013-05-25 08:46:32 +02:00
2013-10-24 11:03:11 -10:00
2013-08-06 22:08:27 -07:00
2013-10-02 17:11:30 +02:00
2013-10-01 16:13:02 +00:00
2012-06-23 22:41:30 -04:00

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

Python client

https://github.com/openstack/python-heatclient

References

We have integration with

Description
OpenStack Orchestration (Heat)
Readme 215 MiB
Languages
Python 99.5%
Shell 0.5%