openstack team mailing list archive

[Mark McLoughlin <markmc@xxxxxxxxxx>]

Hey,

I had the chance to discuss the "global conf" issue with a good number
of folks at the design summit and the conclusion I came away with was
that opinions range from "meh, it's fairly inelegant but I don't care
much either way" to "I actually like the simplicity" to "we use global
conf, it works and we're not changing".

Indeed, at the "common configuration patterns", there was very little in
the way of opinion expressed at all:

  http://etherpad.openstack.org/FolsomCommonConfigPatterns

Given that my goal here is to establish a common pattern used by all
projects, that both Nova and Keystone uses global conf and there isn't a
huge amount of interest in moving away from it, I'm proposing adding
support for it to openstack-common:

  https://blueprints.launchpad.net/openstack-common/+spec/cfg-global-object

Adopting this pattern across all projects will actually help
openstack-common more generally. For example, Russell is moving the RPC
code into openstack-common and it has a bunch of configuration options.
If it can assume a global configuration object, things become much
easier.

I've posted patches to openstack-common, Nova, Glance and Keystone:

  https://review.openstack.org/#/q/status:open+branch:master+topic:bp/cfg-global-object,n,z

Cheers,
Mark.

On Tue, 2012-03-06 at 10:10 +0000, Mark McLoughlin wrote:
> Hey,
> 
> The original cfg design[1] assumed certain usage patterns that I hoped
> would be adopted by all projects using it. In gerrit, we're debating a
> set of patch to make keystone use these patterns:
> 
>   https://review.openstack.org/4547
> 
> I thought it was best to move some of that discussion here since I'm
> hoping we can get some rough consensus across projects. I really think
> it will be beneficial if we can share common idioms and patterns across
> projects, rather than just using the same library in different ways.
[snip]

Thread archived here:

  https://lists.launchpad.net/openstack/msg08329.html