placement/lower-constraints.txt

95 lines
1.6 KiB
Plaintext
Raw Normal View History

alembic==0.9.8
appdirs==1.4.3
attrs==17.4.0
Babel==2.3.4
bandit==1.1.0
colorama==0.3.9
coverage==4.0
debtcollector==1.19.0
decorator==3.4.0
extras==1.0.0
fasteners==0.14.1
fixtures==3.0.0
flake8==2.5.5
future==0.16.0
gabbi==1.35.0
gitdb2==2.0.3
GitPython==2.1.8
hacking==0.12.0
iso8601==0.1.11
Jinja2==2.10
jsonpath-rw==1.4.0
Correct lower-constraints.txt and the related tox job While exploring removing unused packages from lower-constraints.txt it became clear that the lower-constraints job was not working as expected: Because our tox config has usedevelop=True 'setup.py develop' is called to install the placement package after the install command is called. This means that the lower-constraints are clobbered. I had mistakenly assumed that turning off 'usedevelop', which causes 'setup.py install' would not make any difference, because it usually installs dependencies too. It turns out however, that when using pbr and within a git working dir, it does not. That took some time to figure out. Oh well. This change makes it so that we create the tox environment using usedevelop=False and with our own install_command, to avoid upper constraints conflicting with lower constraints. This flagged up a few changes, the main one being that we did not have a new enough version of keystonemiddleware in order to require use of www_authenticate_uri. requirements.txt is updated for this as well. And PasteDeploy needed to be updated to work with Python 3's notion of namespace packages. psycopg2 need a newer version to work with Postgresql 10. oslotest needs to be raised to 3.4.0 because the tests in cmd.test_manage use features to control what is capture by the Output fixture from oslotest. Note that the lower-constraints job found this problem and also demonstrates why we must run the lower-constraints job without upper-constraints being involved. upper-constraints will "win" and we don't want that. The point of the job is find packages where lower-constraints are wrong, so it must "win". The end result here is a lower-constraints.txt file that starts from the lower-constraints.txt defined by nova, and then is adapted to update the versions of packages that were not up to date, remove those packages which are no longer present, and add some that are now required. Change-Id: Id66a28f7ace6fc2adf0e1201d9de5f901234d870
2018-10-31 15:44:16 +00:00
jsonpath-rw-ext==1.1.3
jsonschema==2.6.0
keystoneauth1==3.9.0
Correct lower-constraints.txt and the related tox job While exploring removing unused packages from lower-constraints.txt it became clear that the lower-constraints job was not working as expected: Because our tox config has usedevelop=True 'setup.py develop' is called to install the placement package after the install command is called. This means that the lower-constraints are clobbered. I had mistakenly assumed that turning off 'usedevelop', which causes 'setup.py install' would not make any difference, because it usually installs dependencies too. It turns out however, that when using pbr and within a git working dir, it does not. That took some time to figure out. Oh well. This change makes it so that we create the tox environment using usedevelop=False and with our own install_command, to avoid upper constraints conflicting with lower constraints. This flagged up a few changes, the main one being that we did not have a new enough version of keystonemiddleware in order to require use of www_authenticate_uri. requirements.txt is updated for this as well. And PasteDeploy needed to be updated to work with Python 3's notion of namespace packages. psycopg2 need a newer version to work with Postgresql 10. oslotest needs to be raised to 3.4.0 because the tests in cmd.test_manage use features to control what is capture by the Output fixture from oslotest. Note that the lower-constraints job found this problem and also demonstrates why we must run the lower-constraints job without upper-constraints being involved. upper-constraints will "win" and we don't want that. The point of the job is find packages where lower-constraints are wrong, so it must "win". The end result here is a lower-constraints.txt file that starts from the lower-constraints.txt defined by nova, and then is adapted to update the versions of packages that were not up to date, remove those packages which are no longer present, and add some that are now required. Change-Id: Id66a28f7ace6fc2adf0e1201d9de5f901234d870
2018-10-31 15:44:16 +00:00
keystonemiddleware==4.18.0
linecache2==1.0.0
Mako==1.0.7
MarkupSafe==1.0
mccabe==0.2.1
microversion-parse==0.2.1
mock==2.0.0
monotonic==1.4
mox3==0.20.0
Correct lower-constraints.txt and the related tox job While exploring removing unused packages from lower-constraints.txt it became clear that the lower-constraints job was not working as expected: Because our tox config has usedevelop=True 'setup.py develop' is called to install the placement package after the install command is called. This means that the lower-constraints are clobbered. I had mistakenly assumed that turning off 'usedevelop', which causes 'setup.py install' would not make any difference, because it usually installs dependencies too. It turns out however, that when using pbr and within a git working dir, it does not. That took some time to figure out. Oh well. This change makes it so that we create the tox environment using usedevelop=False and with our own install_command, to avoid upper constraints conflicting with lower constraints. This flagged up a few changes, the main one being that we did not have a new enough version of keystonemiddleware in order to require use of www_authenticate_uri. requirements.txt is updated for this as well. And PasteDeploy needed to be updated to work with Python 3's notion of namespace packages. psycopg2 need a newer version to work with Postgresql 10. oslotest needs to be raised to 3.4.0 because the tests in cmd.test_manage use features to control what is capture by the Output fixture from oslotest. Note that the lower-constraints job found this problem and also demonstrates why we must run the lower-constraints job without upper-constraints being involved. upper-constraints will "win" and we don't want that. The point of the job is find packages where lower-constraints are wrong, so it must "win". The end result here is a lower-constraints.txt file that starts from the lower-constraints.txt defined by nova, and then is adapted to update the versions of packages that were not up to date, remove those packages which are no longer present, and add some that are now required. Change-Id: Id66a28f7ace6fc2adf0e1201d9de5f901234d870
2018-10-31 15:44:16 +00:00
msgpack-python==0.5.6
netaddr==0.7.18
netifaces==0.10.4
os-client-config==1.29.0
Don't use OVO with ResourceProvider and ResourceProviderList Turn ResourceProvider and ResourceProviderList into classical Python objects. There are two changes here which deserve particular attention because they are more changing than the other OVO removals: * There were two deepcopy calls in the allocation request handling. When using OVO, the __deepcopy__ handling built into it prevents deep recursion. I changed them to copy and things still work as expected. This will be because using the nested objects by reference is acceptable. * The removal of OVO removes the detection of changed fields. This was being used when creating and saving resource providers (at the object level) to automagically detect and prevent writing fields we don't want to. This change removes that functionality. Instead if bad data has made it as far as the create or save calls, we simply don't write it. The HTTP layer continues to maintain the guards it already had in place to prevent badness. Tests which were testing the object layer are removed. The create_provider function in functional/db/test_base allowed (trying to) create a provider with a root but that functionality was only called from one place. That place and the functionality in create_provider is removed. Other things to note: * As with the other changes, where context is actually used by the object it is required in the constructor. This cascades some changes to tests. * A test that checks to see if adding traits resets the changes on a rp has been removed, because we don't track that any more if we haven't got OVO. * The last_modified handling in placement/util no longer need NotImplemented handling, that was an artifact of OVO. oslo.versionedobjects is removed from requirements. This doesn't have a huge impact on the size of the virtualenv: 114M -> 107M [1] but it does take us from 132 python dependencies (via pip list) to 119, removing plenty of stuff that was only being called in because stuff that we don't use depended on it. lower-constraints.txt is updated to reflect the removal of dependencies that are no longer needed. [1] Of note, 26M of that is babel. Do we need to translate exceptions? See email disussion at http://lists.openstack.org/pipermail/openstack-discuss/2019-February/thread.html#3002 Change-Id: Ie0a9351e0d7c762c9c96c45cbe50132a0fbd1486
2019-02-14 01:01:15 +00:00
os-resource-classes==0.2.0
os-service-types==1.2.0
os-traits==0.4.0
oslo.concurrency==3.26.0
oslo.config==6.7.0
oslo.context==2.19.2
oslo.db==4.40.0
oslo.i18n==3.15.3
oslo.log==3.36.0
oslo.middleware==3.31.0
oslo.policy==1.35.0
oslo.serialization==2.18.0
oslo.upgradecheck==0.2.0
oslo.utils==3.37.0
Correct lower-constraints.txt and the related tox job While exploring removing unused packages from lower-constraints.txt it became clear that the lower-constraints job was not working as expected: Because our tox config has usedevelop=True 'setup.py develop' is called to install the placement package after the install command is called. This means that the lower-constraints are clobbered. I had mistakenly assumed that turning off 'usedevelop', which causes 'setup.py install' would not make any difference, because it usually installs dependencies too. It turns out however, that when using pbr and within a git working dir, it does not. That took some time to figure out. Oh well. This change makes it so that we create the tox environment using usedevelop=False and with our own install_command, to avoid upper constraints conflicting with lower constraints. This flagged up a few changes, the main one being that we did not have a new enough version of keystonemiddleware in order to require use of www_authenticate_uri. requirements.txt is updated for this as well. And PasteDeploy needed to be updated to work with Python 3's notion of namespace packages. psycopg2 need a newer version to work with Postgresql 10. oslotest needs to be raised to 3.4.0 because the tests in cmd.test_manage use features to control what is capture by the Output fixture from oslotest. Note that the lower-constraints job found this problem and also demonstrates why we must run the lower-constraints job without upper-constraints being involved. upper-constraints will "win" and we don't want that. The point of the job is find packages where lower-constraints are wrong, so it must "win". The end result here is a lower-constraints.txt file that starts from the lower-constraints.txt defined by nova, and then is adapted to update the versions of packages that were not up to date, remove those packages which are no longer present, and add some that are now required. Change-Id: Id66a28f7ace6fc2adf0e1201d9de5f901234d870
2018-10-31 15:44:16 +00:00
oslotest==3.4.0
pbr==2.0.0
pep8==1.5.7
pluggy==0.6.0
ply==3.11
prettytable==0.7.1
Correct lower-constraints.txt and the related tox job While exploring removing unused packages from lower-constraints.txt it became clear that the lower-constraints job was not working as expected: Because our tox config has usedevelop=True 'setup.py develop' is called to install the placement package after the install command is called. This means that the lower-constraints are clobbered. I had mistakenly assumed that turning off 'usedevelop', which causes 'setup.py install' would not make any difference, because it usually installs dependencies too. It turns out however, that when using pbr and within a git working dir, it does not. That took some time to figure out. Oh well. This change makes it so that we create the tox environment using usedevelop=False and with our own install_command, to avoid upper constraints conflicting with lower constraints. This flagged up a few changes, the main one being that we did not have a new enough version of keystonemiddleware in order to require use of www_authenticate_uri. requirements.txt is updated for this as well. And PasteDeploy needed to be updated to work with Python 3's notion of namespace packages. psycopg2 need a newer version to work with Postgresql 10. oslotest needs to be raised to 3.4.0 because the tests in cmd.test_manage use features to control what is capture by the Output fixture from oslotest. Note that the lower-constraints job found this problem and also demonstrates why we must run the lower-constraints job without upper-constraints being involved. upper-constraints will "win" and we don't want that. The point of the job is find packages where lower-constraints are wrong, so it must "win". The end result here is a lower-constraints.txt file that starts from the lower-constraints.txt defined by nova, and then is adapted to update the versions of packages that were not up to date, remove those packages which are no longer present, and add some that are now required. Change-Id: Id66a28f7ace6fc2adf0e1201d9de5f901234d870
2018-10-31 15:44:16 +00:00
psycopg2==2.7
py==1.5.2
pycadf==2.7.0
pyflakes==0.8.1
PyMySQL==0.7.6
pyparsing==2.2.0
pytest==3.4.2
python-dateutil==2.5.3
python-editor==1.0.3
python-keystoneclient==3.15.0
python-mimeparse==1.6.0
python-subunit==1.2.0
pytz==2018.3
PyYAML==3.12
repoze.lru==0.7
requests==2.14.2
requestsexceptions==1.4.0
rfc3986==0.3.1
Routes==2.3.1
six==1.10.0
smmap2==2.0.3
SQLAlchemy==1.0.10
sqlparse==0.2.4
statsd==3.2.2
stestr==1.0.0
stevedore==1.20.0
Tempita==0.5.2
testrepository==0.0.20
testresources==2.0.0
testscenarios==0.4
testtools==2.2.0
traceback2==1.4.0
unittest2==1.1.0
urllib3==1.22
WebOb==1.8.2
wrapt==1.10.11
wsgi-intercept==1.7.0