VIF Binding and Unbinding Mechanism

Registered by Digambar on 2015-08-13

Action Items :-

 create the veth pair
 create the namespace
 Put one end to the namespace and then hand over the other veth to the vif-binding infrastructure (port-type dependant)

We would have -

/usr/libexec/kuryr/bind/name_of_port_type
/usr/libexec/kuryr/unbind/name_of_port_type

Name of port type could be `midonet`, `ovs`, etc.
Eachdriver would have an executable that receives the name of the veth pair that has to be bound to the overlay and the UUID of the Neutron port.
The other pair will be put by kuryr on the container namespace
If binding fails, i.e. it can fail to find the proper bind executable, it should lead to rollback of the top level operation.
     Otherwise there will be unbound port and no connectivity.

I have added etherpad link in specification, if you want to see full details click on "Read the full specification".
Here is etherpad link - https://etherpad.openstack.org/p/Kuryr_vif_binding_unbinding

Blueprint information

Status:
Complete
Approver:
Antoni Segura Puimedon
Priority:
Essential
Drafter:
Digambar
Direction:
Needs approval
Assignee:
Digambar
Definition:
Approved
Series goal:
None
Implementation:
Implemented
Milestone target:
None
Started by
Antoni Segura Puimedon on 2015-08-17
Completed by
Mohammad Banikazemi on 2016-06-09

Related branches

Sprints

Whiteboard

[irenab] - Please add some details regarding the overall workflow that vif binding/unbinding is part of.

Actually etherpad describes everything - diga

Gerrit topic: https://review.openstack.org/#q,topic:bp/vif-binding-and-unbinding-mechanism,n,z

Addressed by: https://review.openstack.org/214002
    [WIP] Implement VIF binding mechanism for kuryr.

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.