Re: [openstack-dev] [oslo] config: deduce related options for config generator?

2016-05-04 Thread Markus Zoeller
> From: Doug Hellmann <d...@doughellmann.com> > To: openstack-dev <openstack-dev@lists.openstack.org> > Date: 05/03/2016 07:04 PM > Subject: Re: [openstack-dev] [oslo] config: deduce related options for > config generator? > > Excerpts from Markus Zoeller's mes

Re: [openstack-dev] [oslo] config: deduce related options for config generator?

2016-05-03 Thread Doug Hellmann
Excerpts from Markus Zoeller's message of 2016-05-03 18:26:50 +0200: > While working on [1] I came across a config option ("pybasedir") > which gets used as a base for many other options, for example > "state_path". The option "state_path" shows then a default value > "state_path = $pybasedir". >

[openstack-dev] [oslo] config: deduce related options for config generator?

2016-05-03 Thread Markus Zoeller
While working on [1] I came across a config option ("pybasedir") which gets used as a base for many other options, for example "state_path". The option "state_path" shows then a default value "state_path = $pybasedir". My question here is, is it possible/reasonable to enhance oslo.config to add an