Add RPC to DSE
Currently, DSE doesn't have any implementations of RPC. It causes:
1) DseRuntime.
2) A deepSix service needs to hold the instance of other services in order to call their interfaces. The "has-a" relationships spread from api models to engine, d6cage, and to synchronizer. These services must run in a single python thread, thus Congress has a scalability problem.
3) The complex dependency between services might block oslo-messaging integration. Services cannot use RPC to communicate with each other.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Yingxin
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
- Tim Hinrichs
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Prototype implementation of RPC in DSE
During the Liberty mid-cycle sprint, we decided to replace the current DSE with an implementation based on oslo.messaging. That decision makes this blueprint obsolete.