yahoo-eng-team team mailing list archive

[YAMAMOTO Takashi <yamamoto@xxxxxxxxxxxx>]

this seems more like a feature request than a bug.

** Changed in: neutron
       Status: New => Opinion

** Changed in: neutron
   Importance: Undecided => Wishlist

** Tags added: rfe

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1855123

Title:
  Neutron ovs agent still fails vlan transparency check

Status in neutron:
  Opinion

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1855123/+subscriptions