Alternative RPC layer implementation
We need to be able not to use oslo.messaging all the time, if needed, for RPC communications. Basically, we can just implement interface from mistral/
The main thing here is to make it convenient and flexible so that we could switch between them using configuration option(s).
Blueprint information
- Status:
- Complete
- Approver:
- Renat Akhmerov
- Priority:
- High
- Drafter:
- Renat Akhmerov
- Direction:
- Approved
- Assignee:
- Dawid Deja
- Definition:
- Approved
- Series goal:
- Accepted for newton
- Implementation:
-
Implemented
- Milestone target:
-
newton-2
- Started by
- Nikolay Makhotkin
- Completed by
- Renat Akhmerov
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
New RPC layer implementation
Addressed by: https:/
Adding OsloRPC server and client
Addressed by: https:/
Make RPC implementation configurable
Addressed by: https:/
Integrating new RPC layer with Mistral
Addressed by: https:/
Add tests for Kombu driver
Addressed by: https:/
Enable 'at-least-once' and 'at-most-once' delivery modes in RPC layer
Addressed by: https:/
Enable 'at-least-once' and 'at-most-once' delivery modes in Engine
Addressed by: https:/
Enable end user to use both delivery modes
Work Items
Dependency tree
* Blueprints in grey have been implemented.
