On Thu, Mar 27, 2014 at 2:21 AM, Dirk Müller <d...@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@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
