<html><body>
<p><font size="2" face="sans-serif">That is great information, thanks Eugene.<br>
</font><br>
<br>
<tt><font size="2">Eugene Nikanorov <enikanorov@mirantis.com> wrote on 05/27/2014 03:51:36 PM:<br>
<br>
> From: Eugene Nikanorov <enikanorov@mirantis.com></font></tt><br>
<tt><font size="2">> To: "OpenStack Development Mailing List (not for usage questions)" <br>
> <openstack-dev@lists.openstack.org>, </font></tt><br>
<tt><font size="2">> Date: 05/27/2014 03:56 PM</font></tt><br>
<tt><font size="2">> Subject: Re: [openstack-dev] [neutron] Supporting retries in neutronclient</font></tt><br>
<tt><font size="2">> <br>
> In fact, nova should be careful about changing number of retries for<br>
> neutron client.</font></tt><br>
<tt><font size="2">> It's known that under significant load (people test serial VM <br>
> creation) neutron client may timeout on POST operation which does <br>
> port creation; retrying this again leads to multiple fixed IPs <br>
> assigned to a VM</font></tt><br>
<tt><font size="2">> <br>
> Thanks,</font></tt><br>
<tt><font size="2">> Eugene.</font></tt><br>
<tt><font size="2">> <br>
</font></tt><br>
<tt><font size="2">> On Wed, May 28, 2014 at 12:09 AM, Kyle Mestery <mestery@noironetworks.com<br>
> > wrote:</font></tt><br>
<tt><font size="2">> I'm not aware of any such change at the moment, no.</font></tt><br>
<tt><font size="2">> <br>
> On Tue, May 27, 2014 at 3:06 PM, Paul Ward <wpward@us.ibm.com> wrote:<br>
> > Great! Do you know if there's any corresponding nova changes to support<br>
> > this as a conf option that gets passed in to this new parm?<br>
> ><br>
> ><br>
> ><br>
> > Kyle Mestery <mestery@noironetworks.com> wrote on 05/27/2014 01:56:12 PM:<br>
> ><br>
> >> From: Kyle Mestery <mestery@noironetworks.com><br>
> >> To: "OpenStack Development Mailing List (not for usage questions)"<br>
> >> <openstack-dev@lists.openstack.org>,<br>
> >> Date: 05/27/2014 02:00 PM<br>
> >> Subject: Re: [openstack-dev] [neutron] Supporting retries in neutronclient<br>
> ><br>
> ><br>
> >><br>
> >> On Tue, May 27, 2014 at 12:48 PM, Paul Ward <wpward@us.ibm.com> wrote:<br>
> >> > Currently, neutronclient is hardcoded to only try a request once in<br>
> >> > retry_request by virtue of the fact that it uses self.retries as the<br>
> >> > retry<br>
> >> > count, and that's initialized to 0 and never changed. We've seen an<br>
> >> > issue<br>
> >> > where we get an ssl handshaking error intermittently (seems like more of<br>
> >> > an<br>
> >> > ssl bug) and a retry would probably have worked. Yet, since<br>
> >> > neutronclient<br>
> >> > only tries once and gives up, it fails the entire operation. Here is<br>
> >> > the<br>
> >> > code in question:<br>
> >> ><br>
> >> > <a href="https://github.com/openstack/python-neutronclient/blob/master/">https://github.com/openstack/python-neutronclient/blob/master/</a><br>
> >> neutronclient/v2_0/client.py#L1296<br>
> >> ><br>
> >> > Does anybody know if there's some explicit reason we don't currently<br>
> >> > allow<br>
> >> > configuring the number of retries? If not, I'm inclined to propose a<br>
> >> > change<br>
> >> > for just that.<br>
> >> ><br>
> >> There is a review to address this in place now [1]. I've given a -1<br>
> >> due to a trivial reason which I hope Jakub will address soon so we can<br>
> >> land this patch in the client code.<br>
> >><br>
> >> Thanks,<br>
> >> Kyle<br>
> >><br>
> >> [1] <a href="https://review.openstack.org/#/c/90104/">https://review.openstack.org/#/c/90104/</a><br>
> >><br>
> >> ><br>
> >> > _______________________________________________<br>
> >> > OpenStack-dev mailing list<br>
> >> > OpenStack-dev@lists.openstack.org<br>
> >> > <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
> >> ><br>
> >><br>
> >> _______________________________________________<br>
> >> OpenStack-dev mailing list<br>
> >> OpenStack-dev@lists.openstack.org<br>
> >> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
> >><br>
> ><br>
> ><br>
> > _______________________________________________<br>
> > OpenStack-dev mailing list<br>
> > OpenStack-dev@lists.openstack.org<br>
> > <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
> ><br>
> <br>
> _______________________________________________<br>
> OpenStack-dev mailing list<br>
> OpenStack-dev@lists.openstack.org<br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a></font></tt><br>
<tt><font size="2">> _______________________________________________<br>
> OpenStack-dev mailing list<br>
> OpenStack-dev@lists.openstack.org<br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</font></tt></body></html>