<div dir="ltr">Why do we need to put all the configuration in a single file?<div><br></div><div>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).</div><div><br></div><div>Best regards,</div><div>Miguel Ángel.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Sep 4, 2017 at 3:01 PM, Kevin Benton <span dir="ltr"><<a href="mailto:kevin@benton.pub" target="_blank">kevin@benton.pub</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">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.<div><br></div><div>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.</div><div><br></div><div>1. <a href="http://logs.openstack.org/82/500182/3/check/gate-puppet-openstack-integration-4-scenario004-tempest-ubuntu-xenial/791523c/logs/etc/neutron/plugins/" target="_blank">http://logs.openstack.org/<wbr>82/500182/3/check/gate-puppet-<wbr>openstack-integration-4-<wbr>scenario004-tempest-ubuntu-<wbr>xenial/791523c/logs/etc/<wbr>neutron/plugins/</a></div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Sep 3, 2017 at 12:03 PM, Mohammed Naser <span dir="ltr"><<a href="mailto:mnaser@vexxhost.com" target="_blank">mnaser@vexxhost.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>On Sun, Sep 3, 2017 at 3:03 PM, Mohammed Naser <<a href="mailto:mnaser@vexxhost.com" target="_blank">mnaser@vexxhost.com</a>> wrote:<br>
> On Sun, Sep 3, 2017 at 2:20 PM, Matthew Treinish <<a href="mailto:mtreinish@kortar.org" target="_blank">mtreinish@kortar.org</a>> wrote:<br>
>> On Sun, Sep 03, 2017 at 01:47:24PM -0400, Mohammed Naser wrote:<br>
>>> Hi folks,<br>
>>><br>
>>> I've attempted to enable mod_wsgi support in our dev environment with<br>
>>> Puppet however it results in a traceback.  I figured it was an<br>
>>> environment thing so I looked into moving the Puppet CI to test using<br>
>>> mod_wsgi and it resulted in the same error.<br>
>>><br>
>>> <a href="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" rel="noreferrer" target="_blank">http://logs.openstack.org/82/5<wbr>00182/3/check/gate-puppet-open<wbr>stack-integration-4-scenario00<wbr>4-tempest-ubuntu-xenial/<wbr>791523c/logs/apache/neutron_<wbr>wsgi_error.txt.gz</a><br>
>>><br>
>>> Would anyone from the Neutron team be able to give input on this?<br>
>>> We'd love to add gating for Neutron deployed by mod_wsgi which can<br>
>>> help find similar issues.<br>
>>><br>
>><br>
>> Neutron never got their wsgi support working in Devstack either. The patch<br>
>> adding that: <a href="https://review.openstack.org/#/c/439191/" rel="noreferrer" target="_blank">https://review.openstack.org/#<wbr>/c/439191/</a> never passed the gate and<br>
>> seems to have lost the attention of the author. The wsgi support in neutron<br>
>> probably doesn't work yet, and is definitely untested. IIRC, the issue they were<br>
>> hitting was loading the config files. [1] I don't think I saw any progress on it<br>
>> after that though.<br>
>><br>
>> The TC goal doc [2] probably should say something about it never landing and<br>
>> missing pike.<br>
>><br>
><br>
> That would make sense.  The release notes also state that it does<br>
> offer the ability to run inside mod_wsgi which can be misleading to<br>
> deployers (that was the main reason I thought we can start testing<br>
> using it):<br>
><br>
</span>Sigh, hit send too early.  Here is the link:<br>
<br>
<a href="http://git.openstack.org/cgit/openstack/neutron/commit/?id=916bc96ee214078496b4b38e1c93f36f906ce840" rel="noreferrer" target="_blank">http://git.openstack.org/cgit/<wbr>openstack/neutron/commit/?id=9<wbr>16bc96ee214078496b4b38e1c93f36<wbr>f906ce840</a><br>
<div class="m_-5477771071394244628HOEnZb"><div class="m_-5477771071394244628h5">><br>
>><br>
>> -Matt Treinish<br>
>><br>
>><br>
>> [1] <a href="http://lists.openstack.org/pipermail/openstack-dev/2017-June/117830.html" rel="noreferrer" target="_blank">http://lists.openstack.org/pip<wbr>ermail/openstack-dev/2017-June<wbr>/117830.html</a><br>
>> [2] <a href="https://governance.openstack.org/tc/goals/pike/deploy-api-in-wsgi.html#neutron" rel="noreferrer" target="_blank">https://governance.openstack.o<wbr>rg/tc/goals/pike/deploy-api-in<wbr>-wsgi.html#neutron</a><br>
>><br>
>> ______________________________<wbr>______________________________<wbr>______________<br>
>> OpenStack Development Mailing List (not for usage questions)<br>
>> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br>
>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
>><br>
<br>
______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
</div></div></blockquote></div><br></div>
</div></div><br>______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
<br></blockquote></div><br></div>