Support NSH dataplane protocol
Bug #1625278 reported by
Igor D.C.
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
networking-sfc |
Fix Released
|
High
|
Igor D.C. |
Bug Description
This RFE is a requirement to achieve https:/
The main changes required are:
- make it possible to select the NSH protocol through the API;
- have NSH protocol support in the SFC OVS agent.
In order to close this bug/RFE, NSH support must be available in upstream Open vSwitch beforehand. Nevertheless, development can be started using the unmerged OVS patches available at https:/
Changed in networking-sfc: | |
assignee: | nobody → Igor Duarte Cardoso (igordcard) |
status: | New → In Progress |
Changed in networking-sfc: | |
assignee: | nobody → Igor Duarte Cardoso (igordcard) |
status: | New → In Progress |
Changed in networking-sfc: | |
importance: | Undecided → High |
milestone: | none → queens-1 |
To post a comment you must log in.
Current discussion in OVS NSH centers around push/pop for the ethernet header in between the NSH and VXLAN headers. A new patch has been posted for review, which uses the following encap format.
VXLAN Hdr + Ethernet + NSH + Original Frame
Please follow the discussion and consensus of NSH in OVS and make sure code in networking-sfc for supporting NSH is in sync with the latest development in OVS.