Difference between revisions of "VPP/OVN"
(→Work list) |
(→Work list) |
||
| Line 25: | Line 25: | ||
| VPP configured to participate in OVN integration bridge. VPP configured separately from agent? | | VPP configured to participate in OVN integration bridge. VPP configured separately from agent? | ||
|- | |- | ||
| − | |Initialise connection to OVSDB | + | | Initialise connection to OVSDB |
| | | | ||
| | | | ||
| Line 31: | Line 31: | ||
| Register in the Physical_Switch table (ports, tunnels) in hardware_vtep database. | | Register in the Physical_Switch table (ports, tunnels) in hardware_vtep database. | ||
|- | |- | ||
| − | |VPP Python interface abstraction | + | | VPP Python interface abstraction |
| | | | ||
| | | | ||
| Line 37: | Line 37: | ||
| Cache and monitor VPP's interface table, VLAN mapping, ACLs etc. | | Cache and monitor VPP's interface table, VLAN mapping, ACLs etc. | ||
|- | |- | ||
| − | |ACL integration | + | | ACL integration |
| − | ||| | + | | |
| − | |Monitor VTEP ACL table and populate ACLs in VPP | + | | |
| + | | | ||
| + | | Monitor VTEP ACL table and populate ACLs in VPP | ||
|- | |- | ||
Revision as of 12:51, 4 July 2017
Project HotDog
Introduction
Integration of OVN and VPP. The initial phase is to integrate VPP as a VTEP gateway to OVN. ovn-controller-vtep is a simple agent written in Python that uses the VTEP OVSDB database on one side and programs the VPP data-plane on the other.
The agent uses the https://github.com/openvswitch/ovs/tree/master/python/ovs OVS Python language binding to communicate with the hardware_vtep database over OVSDB.
ovs.db manages a cached copy of the OVSDB database. We can do something similar for VPP, where the VPP side of the agent maintains a local cached copy of VPP's interfaces, interface state, VLANs etc.
Work list
| Task | Owner | Planned Release | Status | Description |
|---|---|---|---|---|
| Integration Bridge | VPP configured to participate in OVN integration bridge. VPP configured separately from agent? | |||
| Initialise connection to OVSDB | Register in the Physical_Switch table (ports, tunnels) in hardware_vtep database. | |||
| VPP Python interface abstraction | Cache and monitor VPP's interface table, VLAN mapping, ACLs etc. | |||
| ACL integration | Monitor VTEP ACL table and populate ACLs in VPP |
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
