Bug 1465393

Summary: [RFE] Neutron QinQ transparent VLAN support for vBNG usecases
Product: Red Hat OpenStack Reporter: Anita Tragler <atragler>
Component: openstack-neutronAssignee: OSP Team <rhos-maint>
Status: CLOSED WONTFIX QA Contact: Toni Freger <tfreger>
Severity: low Docs Contact:
Priority: unspecified    
Version: 13.0 (Queens)CC: chrisw, egarver, ekuris, ihrachys, mtomaska, scohen, sputhenp, srevivo
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1843935 (view as bug list) Environment:
Last Closed: 2023-09-26 03:27:20 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1843935    

Comment 1 Anita Tragler 2017-06-27 11:29:29 UTC
QinQ is needed for vBNG usecases; requested by Juniper
Where S-VLAN and C-VLAN identify customer and service of the subscriber. They need 16K - 64K QinQ interfaces and will need subscriber level security groups with OVS and OVS-DPDK

Comment 6 Anita Tragler 2020-05-27 14:55:11 UTC
transparent VLAN feature
VLAN aware VMs does not work in this usecase since cloud provider (OpenStack admin) is not aware of the VLAN IDs that the VM application needs or uses
SR-IOV VF does not work when there are large number of VLAN IDs, limited to number of VFs
PCI Pass-thru with PF in VF-trusted is an alternative, but this locks up the NIC, need separate NIC port for each VM application. Not suitable for IT usecases

Comment 15 Red Hat Bugzilla 2024-01-25 04:25:02 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days