Investigate what's involved in remove the <2.0.0 cap for psutil in g-r
Bug #1645918 reported by
Matthew Thode
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Glance |
Fix Released
|
Undecided
|
Unassigned | ||
OpenStack Global Requirements |
Fix Released
|
Undecided
|
Dirk Mueller |
Bug Description
Various projects and distributions would like to move to a newer versions of psutils. psutils was capped in 2014 when 2.0 came out because back then most projects were not compatible with it.
psutil 2.x and above has a lot of API changes as described in:
https:/
In many cases the adjustments are straightforward and can be made in a compatible fashion, allowing us to remove the cap and eventually move
to a higher minimum version.
Changed in openstack-requirements: | |
assignee: | nobody → Dirk Mueller (dmllr) |
description: | updated |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/409140 /git.openstack. org/cgit/ openstack/ glance/ commit/ ?id=06c4313ec0e d043970a60cbbc4 63f3dcad71f6f4
Committed: https:/
Submitter: Jenkins
Branch: master
commit 06c4313ec0ed043 970a60cbbc463f3 dcad71f6f4
Author: Dirk Mueller <email address hidden>
Date: Fri Dec 9 14:11:33 2016 +0100
Adjust test suite for new psutil versions
psutil 2.x and above has a lot of API changes as described in: /github. com/giampaolo/ psutil/ blob/master/ HISTORY. rst
https:/
So we should work correctly with both old and new psutil attributes. This allows to eventually unlift the version
versions by using a version check and use the correct
method/
cap that starts to hurt.
Related-Bug: 1645918 1012f6b7a777ea2 b5cc3a008f6
Change-Id: I6be775e8387627