Re: [openstack-dev] [neutron][nova][oslo] Common backoff & timeout utils

On 4/21/16 1:38 PM, Joshua Harlow wrote: > This might be harder in retrying, but I think I can help u make > something that will work, since retrying has a way to provide a custom > delay function. Thanks for that. My question was if this might be useful as a new backoff in retrying (vs a

Re: [openstack-dev] [neutron][nova][oslo] Common backoff & timeout utils

Boden Russell wrote: I haven't spent much time on this, so the answers below are a first approximation based on a quick visual inspection (e.g. subject to change when I get a chance to hack on some code). On 4/21/16 12:10 PM, Salvatore Orlando wrote: Can you share more details on the "few

Re: [openstack-dev] [neutron][nova][oslo] Common backoff & timeout utils

I haven't spent much time on this, so the answers below are a first approximation based on a quick visual inspection (e.g. subject to change when I get a chance to hack on some code). On 4/21/16 12:10 PM, Salvatore Orlando wrote: > Can you share more details on the "few things we need" that >

Re: [openstack-dev] [neutron][nova][oslo] Common backoff & timeout utils

Boden Russell wrote: On 4/20/16 3:29 PM, Doug Hellmann wrote: Yes, please, let's try to make that work and contribute upstream if we need minor modifications, before we create something new. We can leverage the 'retrying' module (already in global requirements). It lacks a few things we need,

Re: [openstack-dev] [neutron][nova][oslo] Common backoff & timeout utils

Salvatore Orlando wrote: On 21 April 2016 at 16:54, Boden Russell > wrote: On 4/20/16 3:29 PM, Doug Hellmann wrote: > Yes, please, let's try to make that work and contribute upstream if we > need minor modifications, before we create

Re: [openstack-dev] [neutron][nova][oslo] Common backoff & timeout utils

On 21 April 2016 at 16:54, Boden Russell wrote: > On 4/20/16 3:29 PM, Doug Hellmann wrote: > > Yes, please, let's try to make that work and contribute upstream if we > > need minor modifications, before we create something new. > > We can leverage the 'retrying' module

Re: [openstack-dev] [neutron][nova][oslo] Common backoff & timeout utils

On 4/20/16 3:29 PM, Doug Hellmann wrote: > Yes, please, let's try to make that work and contribute upstream if we > need minor modifications, before we create something new. We can leverage the 'retrying' module (already in global requirements). It lacks a few things we need, but those can be

Re: [openstack-dev] [neutron][nova][oslo] Common backoff & timeout utils

FWIW, we were using retrying in oslo.concurrency at one point: https://review.openstack.org/#/c/130872 It looks like that got removed somewhere in the move to fasteners though. On 04/20/2016 04:29 PM, Doug Hellmann wrote: > Excerpts from Chris Dent's message of 2016-04-20 22:16:10 +0100: >> >>

Re: [openstack-dev] [neutron][nova][oslo] Common backoff & timeout utils

On Wed, Apr 20, 2016 at 3:10 PM, Boden Russell wrote: > Today there are a number of places in nova, neutron and perhaps > elsewhere that employ backoff + timeout strategies (see [1] - [4]). > While we are working towards a unified approach in neutron for RPC [5], > it appears

Re: [openstack-dev] [neutron][nova][oslo] Common backoff & timeout utils

[mailto:dava...@gmail.com] Sent: Wednesday, April 20, 2016 4:45 PM To: OpenStack Development Mailing List (not for usage questions) <openstack-dev@lists.openstack.org> Subject: Re: [openstack-dev] [neutron][nova][oslo] Common backoff& timeout utils Sounds good to me Boden. -- Dims On Wed, Apr 20,

Re: [openstack-dev] [neutron][nova][oslo] Common backoff & timeout utils

Excerpts from Chris Dent's message of 2016-04-20 22:16:10 +0100: > > Will the already existing retrying[1] do the job or is it missing > features (the namespacing thing seems like it could be an issue) > or perhaps too generic? > > [1] https://pypi.python.org/pypi/retrying > Yes, please, let's

Re: [openstack-dev] [neutron][nova][oslo] Common backoff & timeout utils

Will the already existing retrying[1] do the job or is it missing features (the namespacing thing seems like it could be an issue) or perhaps too generic? [1] https://pypi.python.org/pypi/retrying -- Chris Dent (�s°□°)�s�喋擤ォ�http://anticdent.org/ freenode: cdent

Re: [openstack-dev] [neutron][nova][oslo] Common backoff & timeout utils

> -Original Message- > From: Davanum Srinivas [mailto:dava...@gmail.com] > Sent: Wednesday, April 20, 2016 4:45 PM > To: OpenStack Development Mailing List (not for usage questions) > <openstack-dev@lists.openstack.org> > Subject: Re: [openstack-dev] [neutron][nova][oslo] Co

Re: [openstack-dev] [neutron][nova][oslo] Common backoff & timeout utils

On Wed, 2016-04-20 at 14:10 -0600, Boden Russell wrote: > Anyone adverse to me crafting an initial oslo patch to kick-off the > details on this one? Have you evaluated any existing solutions in this space? A quick search on PyPi turns up "backoff", which seems to provide several backoff

Re: [openstack-dev] [neutron][nova][oslo] Common backoff & timeout utils

Sounds good to me Boden. -- Dims On Wed, Apr 20, 2016 at 4:10 PM, Boden Russell wrote: > Today there are a number of places in nova, neutron and perhaps > elsewhere that employ backoff + timeout strategies (see [1] - [4]). > While we are working towards a unified approach in

[openstack-dev] [neutron][nova][oslo] Common backoff & timeout utils

Today there are a number of places in nova, neutron and perhaps elsewhere that employ backoff + timeout strategies (see [1] - [4]). While we are working towards a unified approach in neutron for RPC [5], it appears such logic could benefit the greater community as a reusable oslo implementation.