On 03/27/2014 06:10 AM, Robert Collins wrote: > On 27 March 2014 17:30, Tom Fifield <t...@openstack.org> wrote: > >>> Does anyone disagree? >> >> /me raises hand >> >> When I was an operator, I regularly referred to the sample config files >> in the git repository. >> >> If there weren't generated versions of the sample config in the repo, I >> would probably grep the code (not an ideal user experience!). Running >> some random script that I don't know about the existence and might >> depend on having something else installed of is probably not something >> that would happen. > > So, I think its important you have sample configs to refer to. > > Do they need to be in the git repo? > > Note that because libraries now export config options (which is the > root of this problem!) you cannot ever know from the source all the > options for a service - you *must* know the library versions you are > running, to interrogate them for their options.
And how shall we document this properly in the manuals? > We can - and should - have a discussion about the appropriateness of > the layering leak we have today, but in the meantime this is breaking > multiple projects every time any shared library that uses oslo.config > changes any config option... so we need to solve the workflow aspect. Please together with the documentation team. > How about we make a copy of the latest config for each project for > each series - e.g. trunk of everything, Icehouse of servers with trunk > of everything else, etc and make that easily acccessible? Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev