Difference between revisions of "VPP/OVN"
From fd.io
< VPP
| Line 1: | Line 1: | ||
== Project HotDog == | == Project HotDog == | ||
| − | + | === Introduction === | |
Integration of OVN and VPP. The initial phase is to integrate VPP as a VTEP gateway to OVN. | Integration of OVN and VPP. The initial phase is to integrate VPP as a VTEP gateway to OVN. | ||
There will be a simple agent written in Python that uses the VTEP OVSDB database on one side and programs the VPP data-plane on the other. | There will be a simple agent written in Python that uses the VTEP OVSDB database on one side and programs the VPP data-plane on the other. | ||
| − | + | If a packet against all odds does reach VPP (after having been ping-ponged between <n> tables in some openflow setup with a raft of ARP/ND layer violating proxies), VPP will forward the packet onto a VXLAN or Geneve tunnel. Or through a NAT? Or direct if this is IPv6? Of course none of these solutions support IPv6 yet. | |
| − | + | === Work list === | |
| + | |||
| + | # Integration bridge. Create the integration bridge and add the physical interface(s) that is used for logical network connectivity. Done outside of the ovn-gateway-vpp? | ||
| + | # On agent init: Register VPP as a Physical_Switch entry in the VTEP database, update rows with ports and tunnels | ||
| + | |||
| + | |||
| + | |||
| + | === Testing === | ||
Integration tests will be achieved by extending the existing testing tool coming with ovs/ovn (''make check TESTSUITEFLAGS='-k ovn'''). Specific tests cases will be built for that purpose. | Integration tests will be achieved by extending the existing testing tool coming with ovs/ovn (''make check TESTSUITEFLAGS='-k ovn'''). Specific tests cases will be built for that purpose. | ||
| − | + | === Contacts === | |
*Jerome Tollet: jtollet@cisco.com | *Jerome Tollet: jtollet@cisco.com | ||
*Ole Troan: otroan@cisco.com | *Ole Troan: otroan@cisco.com | ||
| − | + | === Useful links === | |
| − | *[http://openvswitch.org/support/dist-docs/vtep.5.html vtep] | + | * [http://openvswitch.org/support/dist-docs/vtep.5.html vtep.5] |
| − | * [http://openvswitch.org/support/dist-docs/ovn-controller-vtep.8.html ovn-controller-vtep] | + | * [http://openvswitch.org/support/dist-docs/ovn-controller-vtep.8.html ovn-controller-vtep.8] |
| + | * [http://openvswitch.org/support/dist-docs/ovn-architecture.7.html ovn-architecture.7] | ||
Revision as of 10:09, 4 July 2017
Project HotDog
Introduction
Integration of OVN and VPP. The initial phase is to integrate VPP as a VTEP gateway to OVN. There will be a simple agent written in Python that uses the VTEP OVSDB database on one side and programs the VPP data-plane on the other.
If a packet against all odds does reach VPP (after having been ping-ponged between <n> tables in some openflow setup with a raft of ARP/ND layer violating proxies), VPP will forward the packet onto a VXLAN or Geneve tunnel. Or through a NAT? Or direct if this is IPv6? Of course none of these solutions support IPv6 yet.
Work list
- Integration bridge. Create the integration bridge and add the physical interface(s) that is used for logical network connectivity. Done outside of the ovn-gateway-vpp?
- On agent init: Register VPP as a Physical_Switch entry in the VTEP database, update rows with ports and tunnels
Testing
Integration tests will be achieved by extending the existing testing tool coming with ovs/ovn (make check TESTSUITEFLAGS='-k ovn'). Specific tests cases will be built for that purpose.
Contacts
- Jerome Tollet: jtollet@cisco.com
- Ole Troan: otroan@cisco.com
