openstack/cyborg
Code Issues Proposed changes

Use new get_rpc_client API from oslo.messaging

Browse Source 
Use the new API that is consistent with
the existing API instead of instantiating the client
class directly.

This was introduced in release 14.1.0 here [1] and
added into oslo.messaging here [2]

[1] https://review.opendev.org/c/openstack/requirements/+/869340
[2] https://review.opendev.org/c/openstack/oslo.messaging/+/862419

Change-Id: I1a0258766757ad3baa4422ed4c51632a4ca0330d
This commit is contained in:
Tobias Urdin 2023-01-19 20:32:07 +00:00
parent eafcc2fc64
commit 6491be0d19
2 changed files with 4 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
cyborg/common/rpc.py
View File

@ -96,9 +96,8 @@ class RequestContextSerializer(messaging.Serializer):
def get_client(target, version_cap=None, serializer=None):
assert TRANSPORT is not None
serializer = RequestContextSerializer(serializer)
return messaging.RPCClient(TRANSPORT,
target,
version_cap=version_cap,
return messaging.get_rpc_client(
TRANSPORT, target, version_cap=version_cap,
serializer=serializer)

2
requirements.txt
View File

@ -10,7 +10,7 @@ oslo.i18n>=1.5.0 # Apache-2.0
oslo.config>=1.1.0,!=4.3.0,!=4.4.0 # Apache-2.0
oslo.log>=5.0.0 # Apache-2.0
oslo.context>=2.9.0 # Apache-2.0
oslo.messaging>=10.3.0 # Apache-2.0
oslo.messaging>=14.1.0 # Apache-2.0
oslo.concurrency>=3.26.0 # Apache-2.0
oslo.service>=1.0.0,!=1.28.1 # Apache-2.0
oslo.db>=10.0.0 # Apache-2.0