Move choosing of pool port from kuryr-controller to kuryr-daemon

Registered by Michal Dulko on 2017-11-17

In the crusade to decrease control plane latency and improve controller downtime behavior, a proposal was made to have:

* A VIF handler in kuryr-controller that only does pool management (e.g creation and deletion of ports in pools) and then updates pool information to the cni daemons. Communication may consist of:
  * Annotating a node.
  * Creating a CRD (Custom Resource Definition) object for each Pool.
  * Creating a CRD object for each port in the Pool.
* a CNI daemon nested VIF driver that loads the existing VIF pool and when requests come just selects VIFs and annotates the pod with the VIF selection (or marks it somehow).

Blueprint information

Status:
Started
Approver:
Antoni Segura Puimedon
Priority:
High
Drafter:
Michal Dulko
Direction:
Approved
Assignee:
Michal Dulko
Definition:
Approved
Series goal:
Accepted for queens
Implementation:
Started
Milestone target:
milestone icon queens-3
Started by
Antoni Segura Puimedon on 2017-11-17

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/daemon-pool-port-choice,n,z

Addressed by: https://review.openstack.org/527242
    Use K8s 1.8 with Hyperkube

Addressed by: https://review.openstack.org/527243
    WiP: Preview of CNI daemon side VIF choice

Addressed by: https://review.openstack.org/525502
    Use K8s 1.8 with Hyperkube

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.