Versioning rpc server and client

Registered by Eli Qiao on 2015-11-18

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

Related branches

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://blueprints.launchpad.net/magnum/+spec/async-rpc-api

Gerrit topic: https://review.openstack.org/#q,topic:bp/versioning-rpc-server,n,z

Addressed by: https://review.openstack.org/247308
    Add conductor manager to handle all RPC handler

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.