[openstack-dev] [all] sample config files should be ignored in git...

Joe Gordon joe.gordon0 at gmail.com
Thu Mar 27 18:54:00 UTC 2014

On Thu, Mar 27, 2014 at 2:21 AM, Dirk Müller <dirk at dmllr.de> wrote:

> Hi,
> >> When I was an operator, I regularly referred to the sample config files
> >> in the git repository.
> The sample config files in git repository are tremendeously useful for
> any operator and OpenStack Packager. Having them generateable with a
> tox line is very cumbersome.
Why is it cumbersome? We do the same thing.

> As a minimum those config files should be part of the sdist tarball
> (aka generated during sdist time).
> > Do they need to be in the git repo?
> IMHO yes, they should go alongside the code change.

Why? We don't include any other automatically generated files (or at least
try not too).

What about if you could just go to docs.openstack.org and find them with a
single click?

> > 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.
> The problem is that we hammer in all the libraries configuration
> option into the main config file. if we'd have "include" support and
> we'd just include the libraries config options that are generated as a
> separate file (and possibly autogenerated) this problem would not
> occur, and it would avoid the gate breakages.
> Thanks,
> Dirk
> _______________________________________________
> 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/20140327/f28bb185/attachment.html>

More information about the OpenStack-dev mailing list