← Back to team overview

openstack team mailing list archive

Re: nova/puppet blueprint, and some questions

 

Please keep model-driven deployment tools in mind while drafting this blueprint.  Tools like rPath.com Cloud Engine integrate with chef/puppet and provide some amazing leverage.  Ultimately, something like it is critical for managing large multi-tenant infrastructures.  Happy to discuss.

Jan




On Jan 30, 2012, at 11:42 AM, Andrew Bogott <abogott@xxxxxxxxxxxxx> wrote:

> For what it's worth:  I've re-worked my original proposal to describe generic package management.  I believe this plan will still suit my specific Puppet aims but is more clearly tool-agnostic (it should work with Chef as well; I welcome suggestions about data format to support other tools.)
> 
> http://wiki.openstack.org/PackageConfigForNova
> 
> And, again, please keep in mind that this design is meant to address /what/ is installed on an instance, not /how/ it gets there.  Obviously 'how' is the interesting part, but I suspect there's too much diversity of usage for any general solution there.
> 
> -Andrew
> 
> 
> 
> On 1/27/12 4:49 AM, Belmiro Moreira wrote:
>> Hi Andrew and others,
>> first of all sorry for my previous email. (seems I sent a unfinished email)
>> 
>> The idea of integrating nova with "configuration management tools"
>> (puppet, chef, ...) is very interesting. But in my opinion we
>> shouldn't have a specific implementation to a single tool or a small
>> set of tools.
>> 
>> <snip>
> 
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
> 


References