<div dir="ltr">On Wed, Jan 21, 2015 at 10:27 AM, Ihar Hrachyshka <span dir="ltr"><<a href="mailto:ihrachys@redhat.com" target="_blank">ihrachys@redhat.com</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"><span class="">
On 01/20/2015 05:40 PM, Paul Michali wrote:<br>
<blockquote type="cite">
<div dir="ltr">Review <a href="https://review.openstack.org/#/c/146508/" target="_blank">https://review.openstack.org/#/c/146508/</a>
is adding support for StrongSwan VPN, which needs mount bind to
be able to specify different paths for config files.
<div><br>
</div>
<div>The code, which used some older patch, does a test for
/proc/1/ns/net, instead of /proc/1/ns/mnt, because it stated
that the latter is only supported in kernel 3.8+. That was a
while ago, and I'm wondering if the condition is still true.
If we know that for Kilo and on, we'll be dealing with 3.8+
kernels, we could use the more accurate test.</div>
<div><br>
</div>
<div>Can we require 3.8+ kernel for this?</div>
</div>
</blockquote>
<br></span>
I think we can but it's better to check with distributions. Red Hat
wise, we ship a kernel that is newer than 3.8.<span class=""><br>
<br>
<blockquote type="cite">
<div dir="ltr">
<div>If so, how and where do we ensure that is true?</div>
</div>
</blockquote>
<br></span>
Ideally, you would implement a sanity check for the feature you need
from the kernel. Though it opens a question of whether we want to
ship multiple sanity check tools for each of repos (neutron + 3 *aas
repos).<br>
<br></div></blockquote><div>If we can consolidate that and use a single tool from the master neutron repository, that would be my vote. <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor="#FFFFFF" text="#000000">
<blockquote type="cite"><span class="">
<div dir="ltr">
<div><br>
</div>
<div>Also, if you can kindly review the code here: <a href="https://review.openstack.org/#/c/146508/5/neutron_vpnaas/services/vpn/common/netns_wrapper.py" target="_blank">https://review.openstack.org/#/c/146508/5/neutron_vpnaas/services/vpn/common/netns_wrapper.py</a>,
I'd really appreciate it, as I'm not versed in the Linux proc
files at all.</div>
<div><br>
</div>
<div>Thanks!</div>
<div><br>
</div>
<div><br clear="all">
<div>
<div>
<div dir="ltr">
<div>
<div dir="ltr">PCM (Paul Michali)</div>
<div dir="ltr">
<div><br>
</div>
<div>IRC............ pc_m (<a href="http://irc.freenode.com" target="_blank">irc.freenode.com</a>)<br>
Twitter....... @pmichali</div>
<div><br>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
<fieldset></fieldset>
<br>
</span><pre>__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
</blockquote>
<br>
</div>
<br>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div></div>