Jump to: navigation, search

TricircleDiscuzZone

Revision as of 01:12, 15 December 2016 by Chaoyi Huang (talk | contribs) (VxLAN L2 networking across Neutron)

VxLAN L2 networking across Neutron

JunSik experiment

wait for Junsik's confirmation whether it's ok to publish it.

tunnel termination point as part of the binding details

Kevin recap for the Barcelona design summit session: http://lists.openstack.org/pipermail/openstack-dev/2016-November/107061.html

L2pop calculates information on the fly to determine tunnel termination endpoints. This is racey (out of order tunnel notifications are not handled) and leads to lots of complexity involving lookups to agent tables, etc. This also makes it very difficult to integrate external devices because they have no way of informing the agents of their tunnel termination endpoint.

We'd like to formalize the tunnel termination point by adding it to the port binding data model just like other encapsulation details (bound segment, segmentation id, etc). This will allow mech drivers to bind ports not based on agents and allow seamless integration with agent-based ports. The L2pop server-side logic would go away since agents would setup forwarding entries just based on the latest data on the port models delivered via push notifications.

This will require some changes on the server side in the port binding process to have the mech drivers provide the tunnel termination point as part of the binding details. The agent side will also require a few changes to have its tunnel forming logic be derived from push notifications instead of tunnel and fdb notifications.