Versioning rpc server and client
Registered by
Eli Qiao
We should give version control of our conductor server and client and keep tracking all api changes.
This need to be done by refactoring magnum conductor.
we may need to add new class ConductorManager to handle all run all rcp handler.
Blueprint information
- Status:
- Not started
- Approver:
- Adrian Otto
- Priority:
- Undefined
- Drafter:
- Eli Qiao
- Direction:
- Approved
- Assignee:
- Eli Qiao
- Definition:
- New
- Series goal:
- None
- Implementation:
- Deferred
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Discussed at 2015-12-01 team meeting. Setting initial priority to Low, pending further input from team discussion. I will not target this to Mitaka without further discussion. --adrian_otto
See also: https:/
Gerrit topic: https:/
Addressed by: https:/
Add conductor manager to handle all RPC handler
(?)