Redesign RPC for async

Registered by hongbin on 2015-11-10

In Tokyo design summit [1], we discussed how to make magnum scalable. A scalability issue was identified: Magnum API makes synchronous RPC calls to conductor could block the API (details in [2]). To address that, we could switch to async RPC calls.

[1] https://etherpad.openstack.org/p/mitaka-magnum-scalability
[2] https://bugs.launchpad.net/magnum/+bug/1510776

Blueprint information

Status:
Complete
Approver:
Adrian Otto
Priority:
High
Drafter:
hongbin
Direction:
Approved
Assignee:
Surojit Pathak
Definition:
Obsolete
Series goal:
Accepted for newton
Implementation:
Needs Code Review
Milestone target:
None
Started by
Adrian Otto on 2015-12-01
Completed by
Adrian Otto on 2016-10-28

Related branches

Sprints

Whiteboard

See also: https://blueprints.launchpad.net/magnum/+spec/versioning-rpc-server

Gerrit topic: https://review.openstack.org/#q,topic:bp/async-container-operations,n,z

Addressed by: https://review.openstack.org/267134
    [WIP]Magnum asynchronous container operation

Gerrit topic: https://review.openstack.org/#q,topic:bp/s,n,z

Addressed by: https://review.openstack.org/275003
    Spec for asynchronous container operations

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.