Add a transport options from client to drivers
Per conversation with Hervé Beraud, Ken Giusti and Ben Nemec.
New feature: Transport Options
With this feature, it is possible to pass parameters to the drivers so that we can use some specific driver options/features.
The idea is to create a generic "transport options", and then each driver will convert from generic to a specific option.
One example is the mandatory flag in RabbitMQ (currently not used, and there is no way to set it).
something like:
```
transport_options = oslo_messaging.
oslo_messaging.
```
The RabbitMQ driver implementation will convert:
at-least-once -----> mandatory=True
Since this feature requires several changes, we split it into three different steps:
1- Add a new parameter called "transport_options" from client to _drivers
2- Implement the drivers decode functions
3- Implement mandatory flag for RabbitMQ
For the other drivers, we will open a new issue.
-
Gabriele Santomaggio
Developer @SUSE
Blueprint information
- Status:
- Not started
- Approver:
- Ken Giusti
- Priority:
- Undefined
- Drafter:
- Gabriele Santomaggio
- Direction:
- Needs approval
- Assignee:
- Gabriele Santomaggio
- Definition:
- Approved
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Bug #1661510: topic_send may loss messages if the queue not exists | In Progress |
Bug #1776492: can oslo_messaging support basic.return | Confirmed |
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Add transport_options parameter
Addressed by: https:/
WIP Implement the transport options
Gerrit topic: https:/
Addressed by: https:/
Add the "transport_options" parameter to the amqp1 and kafka drivers.
Addressed by: https:/
WIP: Implement mandatory flag for RabbitMQ driver
Addressed by: https:/
WIP Add the mandatory flag for direct send
Addressed by: https:/
Add transport_options parameter
Addressed by: https:/
Add transport_options parameter