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

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.

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

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

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

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. On 9/6/17, 9:19 PM, "Thomas Bechtold" wrote: Hi Kevin, On 04.09.2017 15:01, Kevin Benton wrote: >

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

That's still going to be backwards-incompatible with the way it's been shipped for quite a while now. Passing ENV vars or something to point to specific config files is going to need to be explored. On Wed, Sep 6, 2017 at 9:19 PM, Thomas Bechtold wrote: > Hi Kevin, > > On

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

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

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

As a note, in OSP we also include configuration directories and things alike: https://review.rdoproject.org/r/gitweb?p=openstack/neutron-distgit.git;a=blob;f=neutron-server.service;h=e68024cb9dc06e474b1ac9473bff93c3d892b4d6;hb=48a9d1aa77506d0c60d5bc448b7c5c303083aa68#l8 Config directories make

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

Why do we need to put all the configuration in a single file? That would be a big big change to deployers. It'd be great if we can think of an alternate solution. (not sure how that's being handled for other services though). Best regards, Miguel Ángel. On Mon, Sep 4, 2017 at 3:01 PM, Kevin

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

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 locally with my dev environment around the time that RPC server patch went in, but

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

On Sun, Sep 3, 2017 at 2:20 PM, Matthew Treinish wrote: > On Sun, Sep 03, 2017 at 01:47:24PM -0400, Mohammed Naser wrote: >> Hi folks, >> >> I've attempted to enable mod_wsgi support in our dev environment with >> Puppet however it results in a traceback. I figured it was

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

On Sun, Sep 3, 2017 at 3:03 PM, Mohammed Naser wrote: > On Sun, Sep 3, 2017 at 2:20 PM, Matthew Treinish wrote: >> On Sun, Sep 03, 2017 at 01:47:24PM -0400, Mohammed Naser wrote: >>> Hi folks, >>> >>> I've attempted to enable mod_wsgi support in our dev

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

On Sun, Sep 03, 2017 at 01:47:24PM -0400, Mohammed Naser wrote: > Hi folks, > > I've attempted to enable mod_wsgi support in our dev environment with > Puppet however it results in a traceback. I figured it was an > environment thing so I looked into moving the Puppet CI to test using > mod_wsgi

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

Hi folks, I've attempted to enable mod_wsgi support in our dev environment with Puppet however it results in a traceback. I figured it was an environment thing so I looked into moving the Puppet CI to test using mod_wsgi and it resulted in the same error.