<div dir="ltr">Technically we don't need anything in neutron to migrate to a single config files if not rearrange files in ./etc<div>For devstack, iniset calls to plugin-specific configuration files should then be adjusted accordingly.<br>
<div>I think we started with plugin specific configuration files because at that time it looked better to keep "common" arguments separated from the plugin-specific ones.</div><div><br></div><div>From what I gather this could and should be achieved together with the config file generation work. I recall having seen somebody (don't remember who) volunteer for that on IRC.</div>
<div><br></div><div>Salvatore</div><div><br></div><div><br></div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On 2 May 2014 15:18, Kyle Mestery <span dir="ltr"><<a href="mailto:mestery@noironetworks.com" target="_blank">mestery@noironetworks.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On Fri, May 2, 2014 at 6:39 AM, Sean Dague <<a href="mailto:sean@dague.net">sean@dague.net</a>> wrote:<br>
> Some non insignificant number of devstack changes related to neutron<br>
> seem to be neutron plugins having to do all kinds of manipulation of<br>
> extra config files. The grenade upgrade issue in neutron was because of<br>
> some placement change on config files. Neutron seems to have *a ton* of<br>
> config files and is extremely sensitive to their locations/naming, which<br>
> also seems like it ends up in flux.<br>
><br>
> Is there an overview somewhere to explain this design point?<br>
><br>
> All the other services have a single config config file designation on<br>
> startup, but neutron services seem to need a bunch of config files<br>
> correct on the cli to function (see this process list from recent<br>
> grenade run - <a href="http://paste.openstack.org/show/78430/" target="_blank">http://paste.openstack.org/show/78430/</a> note you will have<br>
> to horiz scroll for some of the neutron services).<br>
><br>
> Mostly it would be good to understand this design point, and if it could<br>
> be evolved back to the OpenStack norm of a single config file for the<br>
> services.<br>
><br>
</div></div>I think this is entirely possible. Each plugin has it's own<br>
configuration, and this is usually done in it's own section. In<br>
reality, it's not necessary to have more than a single config file, as<br>
long as the sections in the configuration file are unique.<br>
<br>
I'd like to hear from other Neutron developers on this as well. We<br>
could propose this change for Juno to migrate to a single config file<br>
if everyone agrees.<br>
<br>
Thanks,<br>
Kyle<br>
<div class=""><br>
> -Sean<br>
><br>
> --<br>
> Sean Dague<br>
> <a href="http://dague.net" target="_blank">http://dague.net</a><br>
><br>
><br>
</div>> _______________________________________________<br>
> OpenStack-dev mailing list<br>
> <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote></div><br></div>