Neutron ovs agent still fails vlan transparency check

Bug #1855123 reported by Jing Zhang
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Opinion
Wishlist
Unassigned

Bug Description

OVS has been supporting vlan transparency for a while (since 2.8), see belo

http://www.openvswitch.org/support/dist-docs/ovs-vswitchd.conf.db.5.txt

       other_config : vlan-limit: optional string, containing an integer, at
       least 0
              Limits the number of VLAN headers that can be matched to the
              specified number. Further VLAN headers will be treated as pay‐
              load, e.g. a packet with more 802.1q headers will match Ethernet
              type 0x8100.

              Open vSwitch userspace currently supports at most 2 VLANs, and
              each datapath has its own limit. If vlan-limit is nonzero, it
              acts as a further limit.

              If this value is absent, the default is currently 1. This main‐
              tains backward compatibility with controllers that were designed
              for use with Open vSwitch versions earlier than 2.8, which only
              supported one VLAN.

But Neutron ovs agent still blindly fails the driver capability check, this prevents the OVS feature being used.

    def check_vlan_transparency(self, context):
        """Currently Openvswitch driver doesn't support vlan transparency."""
        return False

Tags: rfe
Revision history for this message
YAMAMOTO Takashi (yamamoto) wrote :

this seems more like a feature request than a bug.

Changed in neutron:
status: New → Opinion
importance: Undecided → Wishlist
tags: added: rfe
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.