support vlan trunk in dragonflow
The VM and docker container may have trunk port, and the packets sent from them may contain different vlan tag, in order to support this scenario, we should support vlan trunk feature in dragonflow.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- hujie
- Direction:
- Needs approval
- Assignee:
- RAJIV KUMAR
- Definition:
- New
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Spec for VLAN aware VMs
Addressed by: https:/
PortSec App to match by reg6 and not in_port
Addressed by: https:/
DHCP App to use unique_key and not ofport
Addressed by: https:/
L3 applications to dispatch packets and not send them
Addressed by: https:/
SG App to match by reg6 instead of in_port
Addressed by: https:/
Metadata to use unique_key rather than in_port
Addressed by: https:/
DNAT app to use unique_key for ICMP packets
Addressed by: https:/
[WIP]Add VLAN aware VMs support to Dragonflow
Addressed by: https:/
Migrate lport to NB models
Addressed by: https:/
db_store2 marks stale objects
Addressed by: https:/
_is_
Addressed by: https:/
nb_api.get to deal with proxy models
Addressed by: https:/
Support copy and deepcopy on proxy objects
Addressed by: https:/
Migrate lport in metadata service daemon
Addressed by: https:/
ARP responder to dispatch packets and not output them
