[openstack-dev] [neutron] mod_wsgi support (pike bug?)
Morales, Victor
victor.morales at intel.com
Fri Sep 15 16:31:48 UTC 2017
Howdy,
Well, my point is that *neutron-server* can be called with several configuration files[1][2][3] as arguments like
$ neutron-server --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/ml2.ini --config-file /root/experimental.ini
Which depends on the needs of the user. Usually these are stored in the same configuration directory but there is no guarantee on that. The other thing that I was thinking is that given that neutron has a pluggable architecute maybe there are config values that define folders to load configuration info, something like *api_extensions_path* which defines the place of the extension classes.
Regards/Saludos
Victor Morales
[1] https://github.com/openstack-dev/devstack/blob/master/lib/neutron#L391-L397
[2] https://github.com/openstack/neutron/blob/master/neutron/server/__init__.py#L30
[3] https://github.com/openstack/neutron/blob/master/neutron/common/config.py#L76-L78
On 9/15/17, 3:23 AM, "Thomas Bechtold" <tbechtold at suse.com> wrote:
Hi Victor,
On 13.09.2017 17:37, Morales, Victor wrote:
> As far as I remember the reason to have everything on a single file is because we’re trying to make Apache to load the configuration values during the startup.
Hm. I don't understand. With config-dirs, the service automatically
reads also the extra files from the directories.
Am I missing something?
Best,
Tom
>
> On 9/6/17, 9:19 PM, "Thomas Bechtold" <tbechtold at suse.com> wrote:
>
> Hi Kevin,
>
> On 04.09.2017 15:01, Kevin Benton wrote:
> > Yes, unfortunately I didn't make it back to the patch in time to adjust
> > devstack to dump all of the configuration into one file (instead of
> > /etc/neutron/neutron.conf /etc/neutron/plugins/ml2.conf etc).
>
> You don't have to put everything into one file. oslo.config supports per
> service config files and conf.d dirs[1].
> So eg. dhcp_agent.ini could be put into
> /etc/neutron/neutron-dhcp-agent.conf.d/foo.conf (it must end with .conf).
> Maybe that's more readable than a single huge config file?
>
> Best,
>
> Tom
>
> [1] https://docs.openstack.org/releasenotes/oslo.config/ocata.html#id2
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
More information about the OpenStack-dev
mailing list