Re: [openstack-dev] [neutron][puppet] mod_wsgi support (pike bug?)

2017-09-05 Thread Kevin Benton
>For the record, oslo.config already reads /etc/neutron/neutron.conf Yeah, I think this is the only reason it even manages to get some of the correct configuration (loading a core plugin at all). >Also for the record, I consider not being able to load existing split >configuration files a

Re: [openstack-dev] [neutron][puppet] mod_wsgi support (pike bug?)

2017-09-05 Thread Ihar Hrachyshka
On Mon, Sep 4, 2017 at 8:07 AM, Kevin Benton wrote: > #2 would be preferable as well just because we have so many guides/distros > mentioning the different file locations. I'm not familiar with mod_wsgi > enough to know if it's possible. > > Another 3rd option may be to edit the

Re: [openstack-dev] [neutron][puppet] mod_wsgi support (pike bug?)

2017-09-05 Thread Kevin Benton
Did you look into setting config files in an env var? That seemed like the best bet given that #2 is out. On Mon, Sep 4, 2017 at 8:19 AM, Mohammed Naser wrote: > On Mon, Sep 4, 2017 at 11:07 AM, Kevin Benton wrote: > > #2 would be preferable as well just

Re: [openstack-dev] [neutron][puppet] mod_wsgi support (pike bug?)

2017-09-04 Thread Mohammed Naser
On Mon, Sep 4, 2017 at 11:07 AM, Kevin Benton wrote: > #2 would be preferable as well just because we have so many guides/distros > mentioning the different file locations. I'm not familiar with mod_wsgi > enough to know if it's possible. I think you might have missed my

Re: [openstack-dev] [neutron][puppet] mod_wsgi support (pike bug?)

2017-09-04 Thread Kevin Benton
Expanding on my other email. We could alter the oslo.config constructor call to pass in file paths from environmental variables as well. Maybe that's the easiest path forward since it would just be a change from sys.argv to the env vars. On Mon, Sep 4, 2017 at 8:04 AM, Mohammed Naser

Re: [openstack-dev] [neutron][puppet] mod_wsgi support (pike bug?)

2017-09-04 Thread Kevin Benton
#2 would be preferable as well just because we have so many guides/distros mentioning the different file locations. I'm not familiar with mod_wsgi enough to know if it's possible. Another 3rd option may be to edit the oslo config constructor call when using that entry point to add some well-known

Re: [openstack-dev] [neutron][puppet] mod_wsgi support (pike bug?)

2017-09-04 Thread Mohammed Naser
On Mon, Sep 4, 2017 at 10:40 AM, Mohammed Naser wrote: > On Mon, Sep 4, 2017 at 9:01 AM, 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 >>

[openstack-dev] [neutron][puppet] mod_wsgi support (pike bug?)

2017-09-04 Thread Mohammed Naser
On Mon, Sep 4, 2017 at 9:01 AM, 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). I did test >