Open Stack

On Thu, Mar 27, 2014 at 5: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.
>

> 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.
>
> > 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.
>

Do we need an "include" directive? We could use the existing --config-dir
option to read more than one file at runtime.

Doug



>
>
> 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/9678d076/attachment.html>