<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jun 10, 2016 at 5:18 PM, Neil Jerram <span dir="ltr"><<a href="mailto:neil@tigera.io" target="_blank">neil@tigera.io</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"><div>Yes, that all makes sense - thanks for explaining.<span class="HOEnZb"><font color="#888888"><br><br></font></span></div><span class="HOEnZb"><font color="#888888"> Neil<br><br></font></span></div><div class="HOEnZb"><div class="h5"><br><div class="gmail_quote"><div dir="ltr">On Fri, Jun 10, 2016 at 3:50 PM Mohammad Banikazemi <<a href="mailto:mb@us.ibm.com" target="_blank">mb@us.ibm.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><p>Hi Neil,<br><br>Currently, when a docker libnetwork "join" operation in Kuryr is returned, it is not guaranteed that the network connectivity has been established. There are containers that check for network connectivity as the first thing they do when they come up and under heavy load some notice there is no connectivity and simply bail out. I am trying to deal with such a use case,<br><br>Thanks for pointing out that option 2 won't work for you. I think Salvatore also alluded to that in his response. What you are suggesting with pinging the container from the appropriate namespace may be worth a try but then there may be containers that do not allow ingress traffic while they are up and happy. So short of what Salvatore suggested in his earlier email (and I am not sure if that can be done without additions to Neutron), we are left with option 1.<br><br>Keep in mind that users can choose not to enable the blocking option and things will be as they are right now. Would that be reasonable?<br></p></div></blockquote></div></div></div></blockquote><div><br></div><div>That means going for the current version in the patch, right?<br> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><p><br>Best,<br><br>Mohammad<br><br><img alt="Inactive hide details for Neil Jerram ---06/10/2016 09:25:59 AM---Hi Mohammad, Why is the blocking needed? Is it to report som" width="16" border="0" height="16"><font color="#424282">Neil Jerram ---06/10/2016 09:25:59 AM---Hi Mohammad, Why is the blocking needed? Is it to report some kind of status back to</font><br><br><font color="#5F5F5F" size="2">From: </font><font size="2">Neil Jerram <<a href="mailto:neil@tigera.io" target="_blank">neil@tigera.io</a>></font><br><font color="#5F5F5F" size="2">To: </font><font size="2">"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a>></font><br><font color="#5F5F5F" size="2">Date: </font><font size="2">06/10/2016 09:25 AM</font></p></div><div><p><br><font color="#5F5F5F" size="2">Subject: </font><font size="2">Re: [openstack-dev] [Kuryr] [Neutron] Waiting until Neutron Port is Active</font><br></p><hr style="color:#8091a5" noshade width="100%" align="left" size="2"><br><br><br><p></p></div><div><p><font size="4">Hi Mohammad,<br></font><br><font size="4">Why is the blocking needed? Is it to report some kind of status back to Docker/Kubernetes, or to allow some follow-on action to happen?<br></font><br><font size="4">When using networking-calico as the driver, I think that only option (1) would work, out of the options you've suggested below. (3) doesn't work, as you say, because Calico doesn't involve an L2 agent. Also Calico doesn't use the RPC message queue for reporting port status, because we've found that that message queue is in itself a scalability bottleneck.<br></font><br><font size="4">I guess another option would be for the using system to determine for itself when the port appears to be working, e.g. by the host pinging the container/pod's IP address.<br></font><br><font size="4">Regards,</font><br><font size="4"> Neil<br></font><br><br><font size="4">On Wed, Jun 8, 2016 at 4:23 PM Mohammad Banikazemi <</font><a href="mailto:mb@us.ibm.com" target="_blank"><u><font color="#0000FF" size="4">mb@us.ibm.com</font></u></a><font size="4">> wrote:</font></p></div><div><p></p><ul><font size="4">For the Kuryr project, in order to support blocking until vifs are plugged in (that is adding config options similar to the following options define in Nova: vif_plugging_is_fatal and vif_plugging_timeout), we need to detect that the Neutron plugin being used is done with plugging a given vif.<br><br>Here are a few options:<br><br>1- The simplest approach seems to be polling for the status of the Neutron port to become Active. (This may lead to scalability issues but short of having a specific goal for scalability, it is not clear that will be the case.)<br>2- Alternatively, We could subscribe to the message queue and wait for such a port update event. <br>3- It was also suggested that we could use l2 agent extension to detect such an event but that seems to limit us to certain Neutron plugins and therefore not acceptable.<br><br>I was wondering if there are other and better options. <br><br>Best,<br><br>Mohammad</font><br><font size="4">__________________________________________________________________________<br>OpenStack Development Mailing List (not for usage questions)<br>Unsubscribe: </font><a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank"><u><font color="#0000FF" size="4">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</font></u></a><u><font color="#0000FF" size="4"><br></font></u></ul><p></p></div><div><p></p><ul><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank"><u><font color="#0000FF" size="4">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</font></u></a><tt>__________________________________________________________________________</tt></ul><p></p></div><div><p></p><ul><tt><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></tt></ul><p></p></div><div><p></p><ul><tt></tt><tt><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></tt><tt><br></tt><br></ul><br>
<p></p></div>
__________________________________________________________________________<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.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote></div>
</div></div><br>__________________________________________________________________________<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.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div></div>