7af22df7dc
We have seen issues with dangling threads in Armada. This is likely due to a bug [0] in the version of gRPC that we were pinned to. This patchset: - moves us to the latest versions of the gRPC python libraries which add a new `channel.close()` method to cleanup channels. - implements the python context manager api in the tiller handler - uses the context manager api to explicitly scope tiller channel creation and cleanup to each Armada API and CLI call. This also fixes a couples issues with error handling introduced in [1]. [0]: https://github.com/grpc/grpc/issues/14338 [1]: https://review.openstack.org/#/c/610384 Change-Id: I2577a20fc76c397aa33157dc12a0e1d36f49733e
35 lines
714 B
Plaintext
35 lines
714 B
Plaintext
deepdiff==3.3.0
|
|
gitpython
|
|
grpcio==1.16.0
|
|
grpcio-tools==1.16.0
|
|
jsonschema>=2.6.0
|
|
keystoneauth1==2.21.0
|
|
keystonemiddleware==4.9.1
|
|
kubernetes>=6.0.0
|
|
Paste>=2.0.3
|
|
PasteDeploy>=1.5.2
|
|
protobuf>=3.4.0
|
|
PyYAML==3.12
|
|
requests
|
|
|
|
# API
|
|
falcon
|
|
uwsgi>=2.0.15
|
|
|
|
# CLI
|
|
click>=6.7
|
|
|
|
# Oslo
|
|
oslo.cache>=1.5.0 # Apache-2.0
|
|
oslo.concurrency>=3.8.0 # Apache-2.0
|
|
oslo.config!=4.3.0,!=4.4.0,>=4.0.0 # Apache-2.0
|
|
oslo.context>=2.14.0 # Apache-2.0
|
|
oslo.db>=4.24.0 # Apache-2.0
|
|
oslo.i18n!=3.15.2,>=2.1.0 # Apache-2.0
|
|
oslo.log>=3.22.0 # Apache-2.0
|
|
oslo.messaging!=5.25.0,>=5.24.2 # Apache-2.0
|
|
oslo.middleware>=3.27.0 # Apache-2.0
|
|
oslo.policy>=1.23.0 # Apache-2.0
|
|
oslo.serialization!=2.19.1,>=1.10.0 # Apache-2.0
|
|
oslo.utils>=3.20.0 # Apache-2.0
|