Replace usage of 'retrying' with 'tenacity'

Bug #1635380 reported by Boden R
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mistral
Fix Released
Undecided
Sharat Sharma

Bug Description

Today a number of OpenStack projects use the 'retrying' library [1] for generic retry behavior. While retrying provides a functional API, its author no longer actively maintains the repo and hasn't responded to numerous PRs, emails, etc. (more discussion in [2]). As a result, we can't push fixes/features to retrying to support various initiatives such as [3].

A fellow stacker graciously forked the retrying repo and revamped it's API to provide greater functionality/pluggablility; called tenacity [4]. While tenacity provides the same functionality as retrying, it has some notable differences such as:
- Tenacity uses seconds rather than ms as retrying did.
- Tenacity has different kwargs for the decorator and
Retrying class itself.
- Tenacity has a different approach for retrying args by
using classes for its stop/wait/retry kwargs.
- By default tenacity raises a RetryError if a retried callable
times out; retrying raises the last exception from the callable.
Tenacity provides backwards compatibility here by offering
the 'reraise' kwarg.
- Tenacity defines 'time.sleep' as a default value for a kwarg.
That said consumers who need to mock patch time.sleep
need to account for this via mocking of time.sleep before
tenacity is imported.
- For retries that check a result, tenacity will raise if the retried
function raises, whereas retrying retried on all exceptions.

We'd like to move from retrying to tenacity and eventually remove retrying from global requirements all together.

For projects using retrying, the move to tenacity (hopefully) isn't overly intrusive, but must take the above differences into consideration.

While I'm working to move all affected projects [6] from retrying to tenacity, this effort is a work in progress (under [5]).

[1] https://github.com/rholder/retrying
[2] https://review.openstack.org/#/c/321867/
[3] http://lists.openstack.org/pipermail/openstack-dev/2016-April/092914.html
[4] https://github.com/jd/tenacity
[5] https://review.openstack.org/#/q/message:%22Replace+retrying+with+tenacity%22
[6] http://codesearch.openstack.org/?q=retrying&i=nope&files=.*.txt&repos=

Boden R (boden)
description: updated
Changed in mistral:
assignee: nobody → Sharat Sharma (sharat-sharma)
Changed in mistral:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to mistral (master)

Fix proposed to branch: master
Review: https://review.openstack.org/398408

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to mistral (master)

Reviewed: https://review.openstack.org/398408
Committed: https://git.openstack.org/cgit/openstack/mistral/commit/?id=c8cb137eb117013f5f84c3ee75d8ff9db61c284b
Submitter: Jenkins
Branch: master

commit c8cb137eb117013f5f84c3ee75d8ff9db61c284b
Author: Sharat Sharma <email address hidden>
Date: Wed Nov 16 20:32:40 2016 +0530

    Replace retrying with tenacity

    We are replacing all usages of the 'retrying' package with
    'tenacity' as the author of retrying is not actively maintaining
    the project. Tenacity is a fork of retrying, but has improved the
    interface and extensibility (see [1] for more details). Our end
    goal here is removing the retrying package from our requirements.

    Tenacity provides the same functionality as retrying, but has the
    following major differences to account for:
    - tenacity uses seconds rather than ms as retrying did.
    - tenacity has different kwargs for the decorator and
    Retrying class itself.
    - tenacity has a different approach for retrying args by
    using classes for its stop/wait/retry kwargs.
    - By default tenacity raises a RetryError if a retried callable
    times out; retrying raises the last exception from the callable.
    Tenacity provides backwards compatibility here by offering
    the 'reraise' kwarg.
    - tenacity defines 'time.sleep' as a default value for a kwarg.
    That said consumers who need to mock patch time.sleep
    need to account for this via mocking of time.sleep before
    tenacity is imported.

    This patch updates all usages of retrying with tenacity.
    Unit tests will be added where applicable.

    Change-Id: I2af3cf024f5391088d602102d9a8039a46415f73
    Closes-Bug: #1635380

Changed in mistral:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/mistral 4.0.0.0b1

This issue was fixed in the openstack/mistral 4.0.0.0b1 development milestone.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.