Open Stack

On 29/04/13 12:34, Angus Salkeld wrote:
> On 29/04/13 09:30 +0100, Steven Hardy wrote:
>> Your example, to me, seems basically a PaaSish pattern, where people want
>> applications to be deployed onto a shared OS platform.  This makes it a
>> pattern we should enable (layered on top of Heat), but not *implement*
>> IMO.
>
> This could be like a AutoScaling LoadConfig, basically a chunk of
> config that gets passed down to a cfn config group. The idea is then
> to be able to share that config snippet by having it in another file
> (nested stack template, with only one Config resource) - not a big
> deal IMO. What would be cool is if you could then pass more than
> one to the Server.
> Why?
> Just from a code reuse point of view. We have a bunch of WordPress
> templates right? How many times do we setup mysql/wordpress? - that is
> dumb.
> Instead we have a mysql-config.template and a
> wordpress-config.template. Then in the
> Wordpress_Single_Instance.template we include both, and in the
> 2_Instance we include one each. This then makes it easier to share
> configurations eventhough the stacks might be a bit different.

Isn't this what Puppet/Chef do already?