openstack team mailing list archive

[Tim Bell <Tim.Bell@xxxxxxx>]

With the Chef and Puppet configurators, I think we cover a large share of the community. I’d suggest that once the formats of the configuration files are settled, we get the associated supporters in Chef-land and Puppet-land to add these to their recipes along with the other folsom changes….

 

Doing something in one component of OpenStack to perform configuration management would actually make our job more difficult as we’ve got the infrastructure with the puppetlabs recipes to deploy and having one configuration management system fighting another is likely to cause more difficulties than it solves.

 

Document the configuration file formats etc. clearly and as consistently as possible with other openstack components but leave the actual configuration to the dedicated devops tools.

 

Tim

 

From: openstack-bounces+tim.bell=cern.ch@xxxxxxxxxxxxxxxxxxx [mailto:openstack-bounces+tim.bell=cern.ch@xxxxxxxxxxxxxxxxxxx] On Behalf Of Doug Hellmann
Sent: 06 June 2012 17:03
To: Julien Danjou
Cc: openstack@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Openstack] [Metering] Agent configuration mechanism

 

 

On Wed, Jun 6, 2012 at 6:36 AM, Julien Danjou <julien.danjou@xxxxxxxxxxxx> wrote:

On Wed, Jun 06 2012, Nick Barcet wrote:

> Maybe the problem of discrepancy of configuration is more an issue for
> metering than for other components? At least that's my belief.

[…]

Sure, I don't say that it's useless to have a centralized configuration
management in our case. I just think that it shouldn't be our problem to
fix that right now, and that we shouldn't spend our energy trying to fix
this.

Attachment: smime.p7s
Description: S/MIME cryptographic signature