tacker/requirements.txt

59 lines
1.9 KiB
Plaintext
Raw Normal View History

# 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.
pbr>=5.5.0 # Apache-2.0
Paste>=2.0.2 # MIT
PasteDeploy>=1.5.0 # MIT
Routes>=2.3.1 # MIT
Fix a failure in tox lower-constraints To resolve a failure in checking lower-constraints on zuul [1], update depending packages as below. * glance-store 0.26.1 is not compatible with jsonschema 3.2.0. It was updated in [2] becuase jsonschema<3.2.0 doesn't support python3.8, so update to introduce glance-store>=2.4.0 for considering running in wallaby [3]. * requests 2.14.2 is not compatible with heat-translator 2.0.0. Although requests>=2.18.0 is required from heat-translator, use 2.20.0 for avoiding another dependency between kubernetes 11.0.0 which requires urllib3>=1.24.2. It's because requests 2.18.0 has dependency 'urllib3<1.22'. * tosca-parser 1.6.0 is not compatible with heat-translator 2.0.0. It is updated to 1.6.1 as required as tosca-parser>=1.6.1. * amqp>=2.4.0,<3.0 should be installed. Add it in `requirements.txt` and amqp==2.4.0 in `lower-constraints.txt`. * keystoneauth1>=3.18.0 and futurist>=2.1.0 are required for openstacksdk 0.44.0. * alembic>=0.9.6 is required for oslo-db 5.0.0. * eventlet!=0.18.3,!=0.20.1,>=0.18.2 is required for glance-store 2.4.0 and oslo-service 1.24.0. * Update tempest 17.1.0 requires jsonschema<3.0.0 to tempest 22.0.0 requires jsonschema>=3.2.0. * Update warlock from 1.3.0 to 1.3.3 for avoiding to download several versions of depending packages might be happend for a recent pip's update [4]. [1] https://zuul.opendev.org/t/openstack/build/fa38f87776d942248fb32ef7c8afe3e2 [2] commit 38a171cc "Cap jsonschema 3.2.0 as the minimal version" [3] https://releases.openstack.org/wallaby/index.html [4] http://pyfound.blogspot.com/2020/11/pip-20-3-new-resolver.html Change-Id: Ib4f9e19450a093c5ed9bd9c68ea7980f98980682 Signed-off-by: Yasufumi Ogawa <yasufum.o@gmail.com>
2020-12-08 01:12:21 +00:00
amqp>=2.4.0
anyjson>=0.3.3 # BSD
Fix a failure in tox lower-constraints To resolve a failure in checking lower-constraints on zuul [1], update depending packages as below. * glance-store 0.26.1 is not compatible with jsonschema 3.2.0. It was updated in [2] becuase jsonschema<3.2.0 doesn't support python3.8, so update to introduce glance-store>=2.4.0 for considering running in wallaby [3]. * requests 2.14.2 is not compatible with heat-translator 2.0.0. Although requests>=2.18.0 is required from heat-translator, use 2.20.0 for avoiding another dependency between kubernetes 11.0.0 which requires urllib3>=1.24.2. It's because requests 2.18.0 has dependency 'urllib3<1.22'. * tosca-parser 1.6.0 is not compatible with heat-translator 2.0.0. It is updated to 1.6.1 as required as tosca-parser>=1.6.1. * amqp>=2.4.0,<3.0 should be installed. Add it in `requirements.txt` and amqp==2.4.0 in `lower-constraints.txt`. * keystoneauth1>=3.18.0 and futurist>=2.1.0 are required for openstacksdk 0.44.0. * alembic>=0.9.6 is required for oslo-db 5.0.0. * eventlet!=0.18.3,!=0.20.1,>=0.18.2 is required for glance-store 2.4.0 and oslo-service 1.24.0. * Update tempest 17.1.0 requires jsonschema<3.0.0 to tempest 22.0.0 requires jsonschema>=3.2.0. * Update warlock from 1.3.0 to 1.3.3 for avoiding to download several versions of depending packages might be happend for a recent pip's update [4]. [1] https://zuul.opendev.org/t/openstack/build/fa38f87776d942248fb32ef7c8afe3e2 [2] commit 38a171cc "Cap jsonschema 3.2.0 as the minimal version" [3] https://releases.openstack.org/wallaby/index.html [4] http://pyfound.blogspot.com/2020/11/pip-20-3-new-resolver.html Change-Id: Ib4f9e19450a093c5ed9bd9c68ea7980f98980682 Signed-off-by: Yasufumi Ogawa <yasufum.o@gmail.com>
2020-12-08 01:12:21 +00:00
eventlet!=0.18.3,!=0.20.1,>=0.18.2 # MIT
requests>=2.25.1 # Apache-2.0
jsonschema>=3.2.0 # MIT
keystonemiddleware>=4.17.0 # Apache-2.0
kombu>=4.3.0 # BSD
netaddr>=0.7.18 # BSD
SQLAlchemy>=1.3.11 # MIT
WebOb>=1.7.1 # MIT
python-heatclient>=1.10.0 # Apache-2.0
python-keystoneclient>=3.8.0 # Apache-2.0
Fix a failure in tox lower-constraints To resolve a failure in checking lower-constraints on zuul [1], update depending packages as below. * glance-store 0.26.1 is not compatible with jsonschema 3.2.0. It was updated in [2] becuase jsonschema<3.2.0 doesn't support python3.8, so update to introduce glance-store>=2.4.0 for considering running in wallaby [3]. * requests 2.14.2 is not compatible with heat-translator 2.0.0. Although requests>=2.18.0 is required from heat-translator, use 2.20.0 for avoiding another dependency between kubernetes 11.0.0 which requires urllib3>=1.24.2. It's because requests 2.18.0 has dependency 'urllib3<1.22'. * tosca-parser 1.6.0 is not compatible with heat-translator 2.0.0. It is updated to 1.6.1 as required as tosca-parser>=1.6.1. * amqp>=2.4.0,<3.0 should be installed. Add it in `requirements.txt` and amqp==2.4.0 in `lower-constraints.txt`. * keystoneauth1>=3.18.0 and futurist>=2.1.0 are required for openstacksdk 0.44.0. * alembic>=0.9.6 is required for oslo-db 5.0.0. * eventlet!=0.18.3,!=0.20.1,>=0.18.2 is required for glance-store 2.4.0 and oslo-service 1.24.0. * Update tempest 17.1.0 requires jsonschema<3.0.0 to tempest 22.0.0 requires jsonschema>=3.2.0. * Update warlock from 1.3.0 to 1.3.3 for avoiding to download several versions of depending packages might be happend for a recent pip's update [4]. [1] https://zuul.opendev.org/t/openstack/build/fa38f87776d942248fb32ef7c8afe3e2 [2] commit 38a171cc "Cap jsonschema 3.2.0 as the minimal version" [3] https://releases.openstack.org/wallaby/index.html [4] http://pyfound.blogspot.com/2020/11/pip-20-3-new-resolver.html Change-Id: Ib4f9e19450a093c5ed9bd9c68ea7980f98980682 Signed-off-by: Yasufumi Ogawa <yasufum.o@gmail.com>
2020-12-08 01:12:21 +00:00
alembic>=0.9.6 # MIT
stevedore>=3.3.0 # Apache-2.0
oslo.concurrency>=3.26.0 # Apache-2.0
oslo.config>=6.8.0 # Apache-2.0
oslo.context>=2.22.0 # Apache-2.0
oslo.db>=5.0.0 # Apache-2.0
oslo.log>=3.36.0 # Apache-2.0
oslo.messaging>=9.3.0 # Apache-2.0
oslo.middleware>=3.31.0 # Apache-2.0
oslo.policy>=3.6.0 # Apache-2.0
oslo.reports>=1.18.0 # Apache-2.0
oslo.rootwrap>=5.8.0 # Apache-2.0
oslo.serialization!=2.19.1,>=2.18.0 # Apache-2.0
oslo.service!=1.28.1,>=1.24.0 # Apache-2.0
oslo.upgradecheck>=1.3.0 # Apache-2.0
oslo.utils>=4.8.0 # Apache-2.0
oslo.versionedobjects>=1.33.3 # Apache-2.0
openstacksdk>=0.44.0 # Apache-2.0
python-neutronclient>=6.7.0 # Apache-2.0
python-novaclient>=9.1.0 # Apache-2.0
rfc3986>=1.2.0 # Apache-2.0
cryptography>=2.7 # BSD/Apache-2.0
paramiko>=2.7.1 # LGPLv2.1+
pyroute2>=0.4.21;sys_platform!='win32' # Apache-2.0 (+ dual licensed GPL2)
python-mistralclient>=4.2.0 # Apache-2.0
python-barbicanclient>=4.5.2 # Apache-2.0
castellan>=0.16.0 # Apache-2.0
Fix missing required parameter when k8s_obj init While deploying CNF(deployment) using pod-affinity rules, a parameter error happended because the topology_key is not assigned when initializing k8s object. This patch fixes this bug by adding the topology_key's default value into `must_param` in translate_outputs._create_k8s_object(). At the same time, in order to deal with the recurrence of this kind of bug, we checked the required parameters of all resources in kubernetes again and added them to must_param. * Kubernetes version: from v1.18.20 to v1.21.1 * Kubernetes-python-client version: v18.20.0 The major changes from the "must_param" used in the previous Wallaby release of Tacker are probably as follows: RuntimeRawExtension The `data` parameter of `V1ControllerRevision`[1] in v11.0.0 was `RuntimeRawExtension`[2], but the `RuntimeRawExtension` was not support for v12.0.0 or later. Therefore `V1ControllerRevision` in v18.20.0[3] it has been changed to` object` type. V1ServiceReference The `service` parameter of `V1APIServiceSpec`[4] in v11.0.0 was `V1ServiceReference`[5], but the `V1ServiceReference` was not support for v12.0.0 or later. Therefore `V1APIServiceSpec` in v18.20.0[6] it has been changed to `ApiregistrationV1ServiceReference`[7]. V1LimitRangeItem The `type` parameter of `V1LimitRangeItem`[8] in v11.0.0 was optional type, but the parameter has changed to must param in v18.20.0[9]. Therefore, the parameter should be added into `must_param`. [1] https://github.com/kubernetes-client/python/blob/v11.0.0/kubernetes/docs/V1ControllerRevision.md [2] https://github.com/kubernetes-client/python/blob/v11.0.0/kubernetes/docs/RuntimeRawExtension.md [3] https://github.com/kubernetes-client/python/blob/v18.20.0/kubernetes/docs/V1ControllerRevision.md [4] https://github.com/kubernetes-client/python/blob/v11.0.0/kubernetes/docs/V1APIServiceSpec.md [5] https://github.com/kubernetes-client/python/blob/v11.0.0/kubernetes/docs/V1ServiceReference.md [6] https://github.com/kubernetes-client/python/blob/v18.20.0/kubernetes/docs/V1APIServiceSpec.md [7] https://github.com/kubernetes-client/python/blob/v18.20.0/kubernetes/docs/ApiregistrationV1ServiceReference.md [8] https://github.com/kubernetes-client/python/blob/v11.0.0/kubernetes/docs/V1LimitRangeItem.md [9] https://github.com/kubernetes-client/python/blob/v18.20.0/kubernetes/docs/V1LimitRangeItem.md Closes-Bug: #1928153 Closes-Bug: #1940602 Change-Id: If77be98d0c4cec6f4c860ae84978f59772f9a6ee
2021-05-13 08:26:56 +00:00
kubernetes>=18.20.0 # Apache-2.0
setuptools!=24.0.0,!=34.0.0,!=34.0.1,!=34.0.2,!=34.0.3,!=34.1.0,!=34.1.1,!=34.2.0,!=34.3.0,!=34.3.1,!=34.3.2,!=36.2.0,>=21.0.0 # PSF/ZPL
tooz>=1.58.0 # Apache-2.0
Fix missing required parameter when k8s_obj init While deploying CNF(deployment) using pod-affinity rules, a parameter error happended because the topology_key is not assigned when initializing k8s object. This patch fixes this bug by adding the topology_key's default value into `must_param` in translate_outputs._create_k8s_object(). At the same time, in order to deal with the recurrence of this kind of bug, we checked the required parameters of all resources in kubernetes again and added them to must_param. * Kubernetes version: from v1.18.20 to v1.21.1 * Kubernetes-python-client version: v18.20.0 The major changes from the "must_param" used in the previous Wallaby release of Tacker are probably as follows: RuntimeRawExtension The `data` parameter of `V1ControllerRevision`[1] in v11.0.0 was `RuntimeRawExtension`[2], but the `RuntimeRawExtension` was not support for v12.0.0 or later. Therefore `V1ControllerRevision` in v18.20.0[3] it has been changed to` object` type. V1ServiceReference The `service` parameter of `V1APIServiceSpec`[4] in v11.0.0 was `V1ServiceReference`[5], but the `V1ServiceReference` was not support for v12.0.0 or later. Therefore `V1APIServiceSpec` in v18.20.0[6] it has been changed to `ApiregistrationV1ServiceReference`[7]. V1LimitRangeItem The `type` parameter of `V1LimitRangeItem`[8] in v11.0.0 was optional type, but the parameter has changed to must param in v18.20.0[9]. Therefore, the parameter should be added into `must_param`. [1] https://github.com/kubernetes-client/python/blob/v11.0.0/kubernetes/docs/V1ControllerRevision.md [2] https://github.com/kubernetes-client/python/blob/v11.0.0/kubernetes/docs/RuntimeRawExtension.md [3] https://github.com/kubernetes-client/python/blob/v18.20.0/kubernetes/docs/V1ControllerRevision.md [4] https://github.com/kubernetes-client/python/blob/v11.0.0/kubernetes/docs/V1APIServiceSpec.md [5] https://github.com/kubernetes-client/python/blob/v11.0.0/kubernetes/docs/V1ServiceReference.md [6] https://github.com/kubernetes-client/python/blob/v18.20.0/kubernetes/docs/V1APIServiceSpec.md [7] https://github.com/kubernetes-client/python/blob/v18.20.0/kubernetes/docs/ApiregistrationV1ServiceReference.md [8] https://github.com/kubernetes-client/python/blob/v11.0.0/kubernetes/docs/V1LimitRangeItem.md [9] https://github.com/kubernetes-client/python/blob/v18.20.0/kubernetes/docs/V1LimitRangeItem.md Closes-Bug: #1928153 Closes-Bug: #1940602 Change-Id: If77be98d0c4cec6f4c860ae84978f59772f9a6ee
2021-05-13 08:26:56 +00:00
PyYAML>=5.4.1 # MIT
PyMySQL>=0.10.1 # MIT
# Glance Store
Fix a failure in tox lower-constraints To resolve a failure in checking lower-constraints on zuul [1], update depending packages as below. * glance-store 0.26.1 is not compatible with jsonschema 3.2.0. It was updated in [2] becuase jsonschema<3.2.0 doesn't support python3.8, so update to introduce glance-store>=2.4.0 for considering running in wallaby [3]. * requests 2.14.2 is not compatible with heat-translator 2.0.0. Although requests>=2.18.0 is required from heat-translator, use 2.20.0 for avoiding another dependency between kubernetes 11.0.0 which requires urllib3>=1.24.2. It's because requests 2.18.0 has dependency 'urllib3<1.22'. * tosca-parser 1.6.0 is not compatible with heat-translator 2.0.0. It is updated to 1.6.1 as required as tosca-parser>=1.6.1. * amqp>=2.4.0,<3.0 should be installed. Add it in `requirements.txt` and amqp==2.4.0 in `lower-constraints.txt`. * keystoneauth1>=3.18.0 and futurist>=2.1.0 are required for openstacksdk 0.44.0. * alembic>=0.9.6 is required for oslo-db 5.0.0. * eventlet!=0.18.3,!=0.20.1,>=0.18.2 is required for glance-store 2.4.0 and oslo-service 1.24.0. * Update tempest 17.1.0 requires jsonschema<3.0.0 to tempest 22.0.0 requires jsonschema>=3.2.0. * Update warlock from 1.3.0 to 1.3.3 for avoiding to download several versions of depending packages might be happend for a recent pip's update [4]. [1] https://zuul.opendev.org/t/openstack/build/fa38f87776d942248fb32ef7c8afe3e2 [2] commit 38a171cc "Cap jsonschema 3.2.0 as the minimal version" [3] https://releases.openstack.org/wallaby/index.html [4] http://pyfound.blogspot.com/2020/11/pip-20-3-new-resolver.html Change-Id: Ib4f9e19450a093c5ed9bd9c68ea7980f98980682 Signed-off-by: Yasufumi Ogawa <yasufum.o@gmail.com>
2020-12-08 01:12:21 +00:00
glance-store>=2.4.0 # Apache-2.0
Change tosca-parser and heat-translator install With devstack, tosca-parser and heat-translator of stable version are installed via pip as listed in `requirements.txt`. However, we usually use devsatck for deploying development env, and it's recommended to get the latest division sometimes. On the other hand, there are not so many cases using stable ones actually. This update includes several tricks as following, but most of them are no need if the two packages have its own devstack script. So, we should remove the tricks after that as described in TODOs added in the update. NOTE: As described below, we should update upper-constraints.txt as following example and upload it to tacker's repo everytime [1] is updated for the change. $ bash devstack/lib/download_upper_consts * Install packages from cloned git repos in `/opt/stack/` as similar to other packages. * Comment out entries of the two packages in `requirements.txt` and `lower-constraints.txt` because no need to install them from here, but activate it if you install stable packages. * To pass tox jobs, add files below. * upper-constraints.txt: The two packages are removed from official constraints file [1] to skip checking version of stable. This file is refreshed everytime running `stack.sh` to catch up the official. * requirements-extra.txt: Install the packages from git repo. Without separating it from `requirements.txt`, `tox -e lower-constraints` is failed. * Update params in `tox.ini` to activate the modifications above. [1] https://releases.openstack.org/constraints/upper/master Signed-off-by: Yasufumi Ogawa <yasufum.o@gmail.com> Change-Id: I776137215ea06c8ac54612d13a663349c2e7db7d
2020-12-01 01:37:04 +00:00
heat-translator>=2.3.0 # Apache-2.0
tosca-parser>=2.3.0 # Apache-2.0