On 08/08/2014 08:42 AM, Nikola Đipanov wrote:
On 08/06/2014 07:54 PM, Jay Pipes wrote:
I bring this up on the mailing list because I think Liyi's patch offers
an interesting future direction to the way that we think about our retry
approach in Nova. Instead of having hard-coded or configurable
On 15/08/14 16:12, Andrew Laski wrote:
On 08/08/2014 08:42 AM, Nikola Đipanov wrote:
On 08/06/2014 07:54 PM, Jay Pipes wrote:
I bring this up on the mailing list because I think Liyi's patch offers
an interesting future direction to the way that we think about our retry
approach in Nova.
On 08/15/2014 11:43 AM, Matthew Booth wrote:
On 15/08/14 16:12, Andrew Laski wrote:
On 08/08/2014 08:42 AM, Nikola Đipanov wrote:
On 08/06/2014 07:54 PM, Jay Pipes wrote:
I bring this up on the mailing list because I think Liyi's patch offers
an interesting future direction to the way that
Hi Nikola,
Thanks a lot for the input! May I kindly invite you to review the change
as well?
BR/Liyi
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
On 08/06/2014 07:54 PM, Jay Pipes wrote:
I bring this up on the mailing list because I think Liyi's patch offers
an interesting future direction to the way that we think about our retry
approach in Nova. Instead of having hard-coded or configurable interval
times, I think Liyi's approach of
Meng
Subject: Re: [openstack-dev] [nova] Deprecating
CONF.block_device_allocate_retries_interval
Maybe we should change how we wait?
I get that we don't want to sit around forever, but perhaps we should
specify a total maximum time to wait instead of a number of iterations
of a loop? Something
On 6 August 2014 18:54, Jay Pipes jaypi...@gmail.com wrote:
So, Liyi Meng has an interesting patch up for Nova:
https://review.openstack.org/#/c/104876
1) We should just deprecate both the options, with a note in the option help
text that these options are not used when volume size is not 0,
Hi Stackers!
So, Liyi Meng has an interesting patch up for Nova:
https://review.openstack.org/#/c/104876
that changes the way that the interval and number of retries is
calculated for a piece of code that waits around for a block device
mapping to become active.
Namely, the patch discards
Maybe we should change how we wait?
I get that we don't want to sit around forever, but perhaps we should
specify a total maximum time to wait instead of a number of iterations
of a loop? Something like 15 minutes should be long enough for
anyone!. Eventlet sleeps are also pretty cheap, so having