-
Epic
-
Resolution: Unresolved
-
Minor
-
None
-
None
-
None
-
None
-
Enable Tap-As-A-Service in Neutron
-
False
-
-
False
-
Proposed
-
Proposed
-
To Do
-
RHOSSTRAT-39 - Support TAPaaS for Neutron in RHOSO 18
-
Committed
-
Proposed
-
43% To Do, 0% In Progress, 57% Done
-
-
-
2024Q3
At present, port mirroring can be accessed from the OVN level. But having the support from the Neutron perspective will make it an end-to-end feature. The plan is to incorporate this end-to-end integration with a new driver in the tap-as-a-service project.
Additionally, investigate the following enhancements and supportability in upstream and downstream.
- OVS performance impact when OVS mirror is enabled. OVS performance should be considered as it impacts customer traffic and OVS mirror should be used temporarily.
- Max egress traffic limit. The mirror traffic plus egress traffic can exceed the NIC port bandwidth (specially for OVS-DPDK), so it should have a mechanism to control and limit the number of mirrors so it does not exceed the max bandwidth limit.
- OVS mirror has to be removed as soon as the mirror traffic endpoint is down, otherwise the flooded mirrored traffic will be overwhelming the transport fabric and impacting the system.