[openstack-dev] [glance] Unifying configuration file

Mark Washenberger mark.washenberger at markwash.net
Wed Jun 18 16:02:54 UTC 2014

On Tue, Jun 17, 2014 at 8:57 AM, Arnaud Legendre <alegendre at vmware.com>

> All the things that you mention here seem to be technical difficulties.
> I don't think technical difficulties should drive the experience of the
> user.
> Also, Zhi Yan seems to be able to make that happen :)


> Thanks,
> Arnaud
> ----- Original Message -----
> From: "Julien Danjou" <julien at danjou.info>
> To: "Arnaud Legendre" <alegendre at vmware.com>
> Cc: "OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev at lists.openstack.org>
> Sent: Tuesday, June 17, 2014 8:43:38 AM
> Subject: Re: [openstack-dev] [glance] Unifying configuration file
> On Tue, Jun 17 2014, Arnaud Legendre wrote:
> > @ZhiYan: I don't like the idea of removing the sample configuration
> file(s)
> > from the git repository. Many people do not want to have to checkout the
> > entire codebase and tox every time they have to verify a variable name
> in a
> > configuration file. I know many people who were really frustrated where
> they
> > realized that the sample config file was gone from the Nova repo.
> > However, I agree with the fact that it would be better if the sample was
> > 100% accurate: so the way I would love to see this working is to generate
> > the sample file every time there is a config change (this being totally
> > automated (maybe at the gate level...)).
> You're a bit late on this. :)
> So what I did these last months (year?) in several project, is to check
> at gate time the configuration file that is automatically generated
> against what's in the patches.
> That turned out to be a real problem because sometimes some options
> changes from the eternal module we rely on (e.g. keystone authtoken or
> oslo.messaging). In the end many projects (like Nova) disabled this
> check altogether, and therefore removed the generated configuration file
> From the git repository.
> > @Julien: I would be interested to understand the value that you see of
> > having only one config file? At this point, I don't see why managing one
> > file is more complicated than managing several files especially when they
> > are organized by categories. Also, scrolling through the registry
> settings
> > every time I want to modify an api setting seem to add some overhead.
> Because there's no way to automatically generate several configuration
> files with each its own set of options using oslo.config.
> Glance is (one of?) the last project in OpenStack to manually write its
> sample configuration file, which are not up to date obviously.
> So really this is mainly about following what every other projects did
> the last year(s).
> --
> Julien Danjou
> -- Free Software hacker
> --
> https://urldefense.proofpoint.com/v1/url?u=http://julien.danjou.info/&k=oIvRg1%2BdGAgOoM1BIlLLqw%3D%3D%0A&r=5wWaXo2oVaivfKLCMyU6Z9UTO8HOfeGCzbGHAT4gZpo%3D%0A&m=a7BLHSmThzpuZ12zhxZOghcz1HWzlQNCbEAXFoAcFSY%3D%0A&s=fe3ff048464bdba926f7da2f19834adba8df90b69fdb2ddd63a35f8288e7fed2
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140618/374a9a26/attachment.html>

More information about the OpenStack-dev mailing list