Open Stack

Markus Zoeller/Germany/IBM at IBMDE wrote on 08/17/2015 09:37:09 AM:

> From: Markus Zoeller/Germany/IBM at IBMDE
> To: "OpenStack Development Mailing List \(not for usage questions\)" 
> <openstack-dev at lists.openstack.org>
> Date: 08/17/2015 09:48 AM
> Subject: Re: [openstack-dev] [openstack][nova] Streamlining of config 
> options in nova
> 
> Michael Still <mikal at stillhq.com> wrote on 08/12/2015 10:08:26 PM:
> 
> > From: Michael Still <mikal at stillhq.com>
> > To: "OpenStack Development Mailing List (not for usage questions)" 
> > <openstack-dev at lists.openstack.org>
> > Date: 08/12/2015 10:14 PM
> > Subject: Re: [openstack-dev] [openstack][nova] Streamlining of config 
> > options in nova
> > [...]
> > 
> > Do we see https://review.openstack.org/#/c/205154/ as a reasonable 
> > example of such centralization? If not, what needs to change there to 
> > make it an example of that centralization? I see value in having a 
> > worked example people can follow before we attempt a large number of 
> > these moves.
> > [...]
> > Michael
> 
> IIUC, this change doesn't yet meet the idea and needs to change by:
> * creating a module "nova/conf/default.py" and
> * move the imagecache config options to that module
> 
> After this change, it wouldn't address the need to lookup which
> services use a specific config option. What about enhancing this to
> something like this:
> [...]

Based on Michael's proposal I did another one which shows what I tried
to describe in the previous mail. 
The example: https://review.openstack.org/#/c/214581/

Regards,
Markus Zoeller (markus_z)