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

[Morales, Victor]

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"  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"  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-requ...@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-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[Thomas Bechtold]

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"  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-requ...@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-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[Morales, Victor]

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:
> 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-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[Kevin Benton]

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 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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[Thomas Bechtold]

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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[Miguel Angel Ajo Pelayo]

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 it a bit more future proof, and able to easily
integrate with vendor plugins without the need to modify the service file.


On Tue, Sep 5, 2017 at 9:27 AM, Miguel Angel Ajo Pelayo  wrote:

> 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 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
>> locally with my dev environment around the time that RPC server patch went
>> in, but there may have been a regression since it went in since it's not
>> tested as Matt pointed out.
>>
>> It appears that puppet is still spreading the config files for the server
>> into multiple locations as well[1]. Does it inherit that logic from
>> devstack? Because that will need to be changed to push all of the relevant
>> server config into one conf.
>>
>> 1. http://logs.openstack.org/82/500182/3/check/gate-puppet-o
>> penstack-integration-4-scenario004-tempest-ubuntu-xenial/
>> 791523c/logs/etc/neutron/plugins/
>>
>> On Sun, Sep 3, 2017 at 12:03 PM, Mohammed Naser 
>> wrote:
>>
>>> 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 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.
>>> >>>
>>> >>> http://logs.openstack.org/82/500182/3/check/gate-puppet-open
>>> stack-integration-4-scenario004-tempest-ubuntu-xenial/791523
>>> c/logs/apache/neutron_wsgi_error.txt.gz
>>> >>>
>>> >>> Would anyone from the Neutron team be able to give input on this?
>>> >>> We'd love to add gating for Neutron deployed by mod_wsgi which can
>>> >>> help find similar issues.
>>> >>>
>>> >>
>>> >> Neutron never got their wsgi support working in Devstack either. The
>>> patch
>>> >> adding that: https://review.openstack.org/#/c/439191/ never passed
>>> the gate and
>>> >> seems to have lost the attention of the author. The wsgi support in
>>> neutron
>>> >> probably doesn't work yet, and is definitely untested. IIRC, the
>>> issue they were
>>> >> hitting was loading the config files. [1] I don't think I saw any
>>> progress on it
>>> >> after that though.
>>> >>
>>> >> The TC goal doc [2] probably should say something about it never
>>> landing and
>>> >> missing pike.
>>> >>
>>> >
>>> > That would make sense.  The release notes also state that it does
>>> > offer the ability to run inside mod_wsgi which can be misleading to
>>> > deployers (that was the main reason I thought we can start testing
>>> > using it):
>>> >
>>> Sigh, hit send too early.  Here is the link:
>>>
>>> http://git.openstack.org/cgit/openstack/neutron/commit/?id=9
>>> 16bc96ee214078496b4b38e1c93f36f906ce840
>>> >
>>> >>
>>> >> -Matt Treinish
>>> >>
>>> >>
>>> >> [1] http://lists.openstack.org/pipermail/openstack-dev/2017-June
>>> /117830.html
>>> >> [2] https://governance.openstack.org/tc/goals/pike/deploy-api-in
>>> -wsgi.html#neutron
>>> >>
>>> >> 
>>> __
>>> >> OpenStack Development Mailing List (not for usage questions)
>>> >> Unsubscribe: openstack-dev-requ...@lists.op
>>> enstack.org?subject:unsubscribe
>>> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>> >>
>>>
>>> 
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe: openstack-dev-requ...@lists.op
>>> enstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
__
OpenStack 

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

[Miguel Angel Ajo Pelayo]

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 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
> locally with my dev environment around the time that RPC server patch went
> in, but there may have been a regression since it went in since it's not
> tested as Matt pointed out.
>
> It appears that puppet is still spreading the config files for the server
> into multiple locations as well[1]. Does it inherit that logic from
> devstack? Because that will need to be changed to push all of the relevant
> server config into one conf.
>
> 1. http://logs.openstack.org/82/500182/3/check/gate-puppet-
> openstack-integration-4-scenario004-tempest-ubuntu-
> xenial/791523c/logs/etc/neutron/plugins/
>
> On Sun, Sep 3, 2017 at 12:03 PM, Mohammed Naser 
> wrote:
>
>> 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 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.
>> >>>
>> >>> http://logs.openstack.org/82/500182/3/check/gate-puppet-open
>> stack-integration-4-scenario004-tempest-ubuntu-xenial/
>> 791523c/logs/apache/neutron_wsgi_error.txt.gz
>> >>>
>> >>> Would anyone from the Neutron team be able to give input on this?
>> >>> We'd love to add gating for Neutron deployed by mod_wsgi which can
>> >>> help find similar issues.
>> >>>
>> >>
>> >> Neutron never got their wsgi support working in Devstack either. The
>> patch
>> >> adding that: https://review.openstack.org/#/c/439191/ never passed
>> the gate and
>> >> seems to have lost the attention of the author. The wsgi support in
>> neutron
>> >> probably doesn't work yet, and is definitely untested. IIRC, the issue
>> they were
>> >> hitting was loading the config files. [1] I don't think I saw any
>> progress on it
>> >> after that though.
>> >>
>> >> The TC goal doc [2] probably should say something about it never
>> landing and
>> >> missing pike.
>> >>
>> >
>> > That would make sense.  The release notes also state that it does
>> > offer the ability to run inside mod_wsgi which can be misleading to
>> > deployers (that was the main reason I thought we can start testing
>> > using it):
>> >
>> Sigh, hit send too early.  Here is the link:
>>
>> http://git.openstack.org/cgit/openstack/neutron/commit/?id=9
>> 16bc96ee214078496b4b38e1c93f36f906ce840
>> >
>> >>
>> >> -Matt Treinish
>> >>
>> >>
>> >> [1] http://lists.openstack.org/pipermail/openstack-dev/2017-June
>> /117830.html
>> >> [2] https://governance.openstack.org/tc/goals/pike/deploy-api-in
>> -wsgi.html#neutron
>> >>
>> >> 
>> __
>> >> OpenStack Development Mailing List (not for usage questions)
>> >> Unsubscribe: openstack-dev-requ...@lists.op
>> enstack.org?subject:unsubscribe
>> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> >>
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[Kevin Benton]

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 there may have been a regression since it went in since it's not
tested as Matt pointed out.

It appears that puppet is still spreading the config files for the server
into multiple locations as well[1]. Does it inherit that logic from
devstack? Because that will need to be changed to push all of the relevant
server config into one conf.

1.
http://logs.openstack.org/82/500182/3/check/gate-puppet-openstack-integration-4-scenario004-tempest-ubuntu-xenial/791523c/logs/etc/neutron/plugins/

On Sun, Sep 3, 2017 at 12:03 PM, Mohammed Naser  wrote:

> 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 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.
> >>>
> >>> http://logs.openstack.org/82/500182/3/check/gate-puppet-
> openstack-integration-4-scenario004-tempest-ubuntu-
> xenial/791523c/logs/apache/neutron_wsgi_error.txt.gz
> >>>
> >>> Would anyone from the Neutron team be able to give input on this?
> >>> We'd love to add gating for Neutron deployed by mod_wsgi which can
> >>> help find similar issues.
> >>>
> >>
> >> Neutron never got their wsgi support working in Devstack either. The
> patch
> >> adding that: https://review.openstack.org/#/c/439191/ never passed the
> gate and
> >> seems to have lost the attention of the author. The wsgi support in
> neutron
> >> probably doesn't work yet, and is definitely untested. IIRC, the issue
> they were
> >> hitting was loading the config files. [1] I don't think I saw any
> progress on it
> >> after that though.
> >>
> >> The TC goal doc [2] probably should say something about it never
> landing and
> >> missing pike.
> >>
> >
> > That would make sense.  The release notes also state that it does
> > offer the ability to run inside mod_wsgi which can be misleading to
> > deployers (that was the main reason I thought we can start testing
> > using it):
> >
> Sigh, hit send too early.  Here is the link:
>
> http://git.openstack.org/cgit/openstack/neutron/commit/?id=
> 916bc96ee214078496b4b38e1c93f36f906ce840
> >
> >>
> >> -Matt Treinish
> >>
> >>
> >> [1] http://lists.openstack.org/pipermail/openstack-dev/2017-
> June/117830.html
> >> [2] https://governance.openstack.org/tc/goals/pike/deploy-api-
> in-wsgi.html#neutron
> >>
> >> 
> __
> >> OpenStack Development Mailing List (not for usage questions)
> >> Unsubscribe: openstack-dev-requ...@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-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[Mohammed Naser]

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 an
>> environment thing so I looked into moving the Puppet CI to test using
>> mod_wsgi and it resulted in the same error.
>>
>> http://logs.openstack.org/82/500182/3/check/gate-puppet-openstack-integration-4-scenario004-tempest-ubuntu-xenial/791523c/logs/apache/neutron_wsgi_error.txt.gz
>>
>> Would anyone from the Neutron team be able to give input on this?
>> We'd love to add gating for Neutron deployed by mod_wsgi which can
>> help find similar issues.
>>
>
> Neutron never got their wsgi support working in Devstack either. The patch
> adding that: https://review.openstack.org/#/c/439191/ never passed the gate 
> and
> seems to have lost the attention of the author. The wsgi support in neutron
> probably doesn't work yet, and is definitely untested. IIRC, the issue they 
> were
> hitting was loading the config files. [1] I don't think I saw any progress on 
> it
> after that though.
>
> The TC goal doc [2] probably should say something about it never landing and
> missing pike.
>

That would make sense.  The release notes also state that it does
offer the ability to run inside mod_wsgi which can be misleading to
deployers (that was the main reason I thought we can start testing
using it):


>
> -Matt Treinish
>
>
> [1] http://lists.openstack.org/pipermail/openstack-dev/2017-June/117830.html
> [2] 
> https://governance.openstack.org/tc/goals/pike/deploy-api-in-wsgi.html#neutron
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[Mohammed Naser]

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 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.
>>>
>>> http://logs.openstack.org/82/500182/3/check/gate-puppet-openstack-integration-4-scenario004-tempest-ubuntu-xenial/791523c/logs/apache/neutron_wsgi_error.txt.gz
>>>
>>> Would anyone from the Neutron team be able to give input on this?
>>> We'd love to add gating for Neutron deployed by mod_wsgi which can
>>> help find similar issues.
>>>
>>
>> Neutron never got their wsgi support working in Devstack either. The patch
>> adding that: https://review.openstack.org/#/c/439191/ never passed the gate 
>> and
>> seems to have lost the attention of the author. The wsgi support in neutron
>> probably doesn't work yet, and is definitely untested. IIRC, the issue they 
>> were
>> hitting was loading the config files. [1] I don't think I saw any progress 
>> on it
>> after that though.
>>
>> The TC goal doc [2] probably should say something about it never landing and
>> missing pike.
>>
>
> That would make sense.  The release notes also state that it does
> offer the ability to run inside mod_wsgi which can be misleading to
> deployers (that was the main reason I thought we can start testing
> using it):
>
Sigh, hit send too early.  Here is the link:

http://git.openstack.org/cgit/openstack/neutron/commit/?id=916bc96ee214078496b4b38e1c93f36f906ce840
>
>>
>> -Matt Treinish
>>
>>
>> [1] http://lists.openstack.org/pipermail/openstack-dev/2017-June/117830.html
>> [2] 
>> https://governance.openstack.org/tc/goals/pike/deploy-api-in-wsgi.html#neutron
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[Matthew Treinish]

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 and it resulted in the same error.
> 
> http://logs.openstack.org/82/500182/3/check/gate-puppet-openstack-integration-4-scenario004-tempest-ubuntu-xenial/791523c/logs/apache/neutron_wsgi_error.txt.gz
> 
> Would anyone from the Neutron team be able to give input on this?
> We'd love to add gating for Neutron deployed by mod_wsgi which can
> help find similar issues.
> 

Neutron never got their wsgi support working in Devstack either. The patch
adding that: https://review.openstack.org/#/c/439191/ never passed the gate and
seems to have lost the attention of the author. The wsgi support in neutron
probably doesn't work yet, and is definitely untested. IIRC, the issue they were
hitting was loading the config files. [1] I don't think I saw any progress on it
after that though.

The TC goal doc [2] probably should say something about it never landing and
missing pike.

-Matt Treinish


[1] http://lists.openstack.org/pipermail/openstack-dev/2017-June/117830.html
[2] 
https://governance.openstack.org/tc/goals/pike/deploy-api-in-wsgi.html#neutron


signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[Mohammed Naser]

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.

http://logs.openstack.org/82/500182/3/check/gate-puppet-openstack-integration-4-scenario004-tempest-ubuntu-xenial/791523c/logs/apache/neutron_wsgi_error.txt.gz

Would anyone from the Neutron team be able to give input on this?
We'd love to add gating for Neutron deployed by mod_wsgi which can
help find similar issues.

Thanks in advance,
Mohammed

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev