Open Stack

On 12/06/2011 12:06 PM, Jay Pipes wrote:
> On Tue, Dec 6, 2011 at 2:22 PM, John Dickinson
> <john.dickinson at rackspace.com> wrote:
>> Overall, I think it's a great thing to have commonality between the projects on option names and environment variables. I think it's worthwhile to push for that in the swift cli tool in the essex timeframe.
>>
>> On the topic of common config libraries, though, I think the differences are less important. Mark's wiki page describing a common config library sounds interesting, but I agree with Monty that it may be better to be a separate (ie non-openstack) module.
> 
> Could you explain the above a bit more? Mark has already posted code
> for a common config module and I think the idea is to have it live in
> the openstack-common Python library and have Nova, Glance and Swift
> import that openstack.common library...

I think (iirc) that markmc and I were talking about both an ultimate
ending point and a way to get there.

As in - start with the code in openstack-common for right now, get
things working, get everything happy.

THEN - because this is actually missing the python world in general, we
can perhaps pull out the functionality into a library that we land
either on pypi or even (if I have my way) in python core. Then
openstack.common could just consume that.

But a decision on the eventual home of a sensible library which handles
both config files and command line options shouldn't really block us
from moving forward on intra-project collaboration at the moment.

Monty