<div dir="ltr">On Tue, May 23, 2017 at 11:18 AM, Juan Antonio Osorio <span dir="ltr"><<a href="mailto:jaosorior@gmail.com" target="_blank">jaosorior@gmail.com</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote"><span class="gmail-">On Tue, May 23, 2017 at 8:23 AM, Rabi Mishra <span dir="ltr"><<a href="mailto:ramishra@redhat.com" target="_blank">ramishra@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><div><div>Hi All,<br><br></div>As per the updated community goal[1]  for api deployment with wsgi, we've to transition to use uwsgi rather than mod_wsgi at the gate. It also seems mod_wsgi support would be removed from devstack in Queens.<br></div></div></div></blockquote></span><div>What do you mean support for mod_wsgi will be removed from devstack in Queens? other projects have been using mod_wsgi and we've been deploying several services (even Heat) in TripleO.</div></div></div></div></blockquote><div><br></div><div>I think it's mentioned in the community goal I linked earlier -  "with the intent that the <code class="gmail-docutils gmail-literal"><span class="gmail-pre">mod_wsgi</span></code> support is deleted from devstack
in Queens". Atleast that's the intent I assume;)<br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div> <br></div><span class="gmail-"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><div><br></div>I've been working on a patch[2] for the transition and encountered a few issues as below.<br><br>1. We encode stack_indentifer(<stack_name/s<wbr>tack_id> along with the path separator in heatclient. So, requests with encoded path separators are dropped by apache (with 404), if we don't have 'AllowEncodedSlashes On' directive in the site/vhost config[3].<br></div></div></blockquote></span><div>That's correct. You might want to refer to the configuration we use in puppet/TripleO. We got it working with that :).  <a href="https://github.com/openstack/puppet-heat/blob/master/manifests/wsgi/apache.pp#L111-L137" target="_blank">https://github.com/openstack/<wbr>puppet-heat/blob/master/<wbr>manifests/wsgi/apache.pp#L111-<wbr>L137</a> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="gmail-"><div dir="ltr"><div><br></div><div>Setting this for mod_proxy_uwsgi[4] seems to work on fedora but not ubuntu.  From my testing It seems, it has to be set in 000-default.conf for ubuntu.  <br><br>Rather than messing with the devstack plugin code, I went ahead proposed a change to not encode the path separators in heatclient[5] ( Anyway they would be decoded by apache with the directive 'AllowEncodedSlashes On' before it's consumed by the service) which seem to have fixed those 404s.<br><br>Is there a generic way to set the above directive (when using apache+mod_proxy_uwsgi) in the devstack plugin?<br></div><div><br></div><div>2.  With the above, most of the tests seem to work fine other than the ones using waitcondition, where we signal back from the vm to the api services. I could see " <span class="gmail-m_-4413102913215718210gmail-m_-6772840735886532414gmail-NONE gmail-m_-4413102913215718210gmail-m_-6772840735886532414gmail-_2017-05-20_07_04_30_718021 gmail-m_-4413102913215718210gmail-m_-6772840735886532414gmail-highlight">curl: (7) Failed to connect to 10.0.1.78 port 80: No route to host</span>" in the vm console logs[6].<br><br></div><div>It could connect to heat api services using ports 8004/8000 without this patch, but not sure why not port 80? I tried testing this locally and didn't see the issue though. <br><br>Is this due to some infra settings or something else?<br></div><div><br><br>[1] <a href="https://governance.openstack.org/tc/goals/pike/deploy-api-in-wsgi.html" target="_blank">https://governance.openstack.o<wbr>rg/tc/goals/pike/deploy-api-in<wbr>-wsgi.html</a><br><br>[2] <a href="https://review.openstack.org/#/c/462216/" target="_blank">https://review.openstack.org/#<wbr>/c/462216/</a><br><br>[3]  <a href="https://github.com/openstack/heat/blob/master/devstack/files/apache-heat-api.template#L9" target="_blank">https://github.com/openstack/h<wbr>eat/blob/master/devstack/files<wbr>/apache-heat-api.template#L9</a><br clear="all"><div><div><div><div><br>[4] <a href="http://logs.openstack.org/16/462216/6/check/gate-heat-dsvm-functional-convg-mysql-lbaasv2-non-apache-ubuntu-xenial/fbd06d6/logs/apache_config/heat-wsgi-api.conf.txt.gz" target="_blank">http://logs.openstack.org/16/4<wbr>62216/6/check/gate-heat-dsvm-f<wbr>unctional-convg-mysql-lbaasv2-<wbr>non-apache-ubuntu-xenial/<wbr>fbd06d6/logs/apache_config/<wbr>heat-wsgi-api.conf.txt.gz</a><br><br>[5] <a href="https://review.openstack.org/#/c/463510/" target="_blank">https://review.openstack.org/#<wbr>/c/463510/</a><br><br>[6] <a href="http://logs.openstack.org/16/462216/11/check/gate-heat-dsvm-functional-convg-mysql-lbaasv2-non-apache-ubuntu-xenial/e7d9e90/console.html#_2017-05-20_07_04_30_718021" target="_blank">http://logs.openstack.org/16/4<wbr>62216/11/check/gate-heat-dsvm-<wbr>functional-convg-mysql-lbaasv2<wbr>-non-apache-ubuntu-xenial/<wbr>e7d9e90/console.html#_2017-05-<wbr>20_07_04_30_718021</a><span class="gmail-m_-4413102913215718210gmail-HOEnZb"><font color="#888888"><br><br><br>-- <br><div class="gmail-m_-4413102913215718210gmail-m_-6772840735886532414gmail_signature"><div dir="ltr"><div>Regards,</div>Rabi Mishra<div><br></div></div></div>
</font></span></div></div></div></div></div></div>
<br></span>______________________________<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></blockquote></div><span class="gmail-HOEnZb"><font color="#888888"><br><br clear="all"><br>-- <br><div class="gmail-m_-4413102913215718210gmail_signature"><div dir="ltr"><div><font style="font-family:arial narrow,sans-serif;color:rgb(102,102,102)" size="2">Juan Antonio Osorio R.<br>e-mail: <a href="mailto:jaosorior@gmail.com" target="_blank">jaosorior@gmail.com</a><br></font><font style="font-family:arial narrow,sans-serif;color:rgb(102,102,102)" size="2"><br></font></div></div></div>
</font></span></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><br clear="all"><br>-- <br><div class="gmail_signature"><div dir="ltr"><div>Regards,</div>Rabi Misra<div><br></div></div></div>
</div></div>