Open Stack

Excerpts from Thomas Herve's message of 2014-01-30 03:01:38 -0800:
> Hi all,
> 
> While talking to Zane yesterday, he raised an interesting question about whether or not we want to keep a LaunchConfiguration object for the native autoscaling resources.
> 
> The LaunchConfiguration object basically holds properties to be able to fire new servers in a scaling group. In the new design, we will be able to start arbitrary resources, so we can't keep a strict LaunchConfiguration object as it exists, as we can have arbitrary properties.
> 

IIRC, LaunchConfiguration is just part of the API for AWS's separate
auto scaling service.

Since we're auto scaling in Heat we have template intelligence in our
auto scaler and thus we shouldn't need two resources.