Drop lower-constraints.txt and its testing

As discussed in TC PTG[1] and TC resolution[2], we are
dropping the lower-constraints.txt file and its testing.
We will keep lower bounds in the requirements.txt file but
with a note that these are not tested lower bounds and we
try our best to keep them updated.

[1] https://etherpad.opendev.org/p/tc-zed-ptg#L326
[2] https://governance.openstack.org/tc/resolutions/20220414-drop-lower-constraints.html#proposal

Change-Id: Ide6b3e9d6c1171f1ae568c256a3e9affa45de17b
This commit is contained in:
Ghanshyam Mann 2022-04-30 17:58:31 -05:00
parent 4cf0147e86
commit 2e94aa4241
4 changed files with 4 additions and 68 deletions

View File

@ -1,61 +0,0 @@
alembic==1.4.2
automaton==1.9.0
Babel==2.6.0
bandit==1.1.0
cliff==3.3.0
coverage==4.0
ddt==1.2.1
dogpile.cache==0.9.2
eventlet==0.18.2
fixtures==3.0.0
futurist==1.2.0
ironic-lib==4.6.1
iso8601==0.1.11
Jinja2==3.0.0
jsonpatch==1.16
jsonschema==3.2.0
keystoneauth1==4.2.0
keystonemiddleware==4.17.0
openstacksdk==0.48.0
oslo.concurrency==4.2.0
oslo.config==6.8.0
oslo.context==2.22.0
oslo.db==9.1.0
oslo.i18n==3.20.0
oslo.log==4.3.0
oslo.messaging==5.29.0
oslo.middleware==3.31.0
oslo.policy==3.7.0
oslo.reports==1.18.0
oslo.rootwrap==5.8.0
oslo.serialization==2.25.0
oslo.service==1.24.0
oslotest==3.2.0
oslo.upgradecheck==1.3.0
oslo.utils==4.5.0
oslo.versionedobjects==1.31.2
osprofiler==1.5.0
os-traits==0.4.0
pbr==3.1.1
pecan==1.0.0
psutil==3.2.2
psycopg2==2.8.5
pycdlib==1.11.0
PyMySQL==0.8.0
pysnmp==4.4.12
python-cinderclient==3.3.0
python-glanceclient==2.8.0
python-swiftclient==3.2.0
pytz==2013.6
requests==2.18.0
rfc3986==1.2.0
SQLAlchemy==1.2.19
stestr==2.0.0
stevedore==1.29.0
sushy==3.10.0
tenacity==6.2.0
testtools==2.2.0
tooz==2.7.0
virtualbmc==1.4.0
WebOb==1.7.1
WebTest==2.0.27

View File

@ -1,3 +1,7 @@
# Requirements lower bounds listed here are our best effort to keep them up to
# date but we do not test them so no guarantee of having them all correct. If
# you find any incorrect lower bounds, let us know or propose a fix.
# The order of packages is significant, because pip processes them in the order
# of appearance. Changing the order has an impact on the overall integration
# process, which may cause wedges in the gate later.

View File

@ -154,9 +154,3 @@ paths = ./ironic/hacking/
usedevelop = False
deps = -r{toxinidir}/test-requirements.txt
commands = bandit -r ironic -x tests -n5 -ll -c tools/bandit.yml
[testenv:lower-constraints]
deps =
-c{toxinidir}/lower-constraints.txt
-r{toxinidir}/test-requirements.txt
-r{toxinidir}/requirements.txt

View File

@ -2,7 +2,6 @@
templates:
- check-requirements
- openstack-cover-jobs
- openstack-lower-constraints-master-branch-jobs
- openstack-python3-zed-jobs
- openstack-python3-zed-jobs-arm64
- periodic-stable-jobs