Open Stack

On 17/06/14 23:43, Julien Danjou wrote:
> 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.

...and users absolutely hated this. Please refer to the comments on the 
recent cinder patch to remove cinder.conf.sample: 
https://review.openstack.org/#/c/96581/ , and please find out a way 
forward for glance that also makes users happy :)

Regards,

Tom