Support virtual tunnel port in Dragonflow
OVS supports not specifying remote_ip in the tunnel port, and designating dest address in the OpenFlow. Dragonflow can use this feature, and just create one tunnel port for each tunnel type. This saves dragonflow from managing tunnel ports especially when the topology is huge. Also, it mitigates the burden of ovsdb.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Hong Hui Xiao
- Direction:
- Needs approval
- Assignee:
- Hong Hui Xiao
- Definition:
- Approved
- Series goal:
- None
- Implementation:
-
Implemented
- Milestone target:
- None
- Started by
- Hong Hui Xiao
- Completed by
- Hong Hui Xiao
Related branches
Related bugs
Sprints
Whiteboard
xiaohhui: 2017-01-12 all patches merged, the functionality is working now.
Gerrit topic: https:/
Addressed by: https:/
Spec for virtual tunnel port implementation
Addressed by: https:/
Create virtual tunnel port when specified
Addressed by: https:/
Add chassis in db_store
Addressed by: https:/
Apply virtual tunnel port to l2 app
Addressed by: https:/
Use same priority for remote port's multicast flow
Addressed by: https:/
Remove the legacy tunnel port code.
