yahoo-eng-team team mailing list archive

[Launchpad Bug Tracker <1525059@xxxxxxxxxxxxxxxxxx>]

[Expired for neutron because there has been no activity for 60 days.]

** Changed in: neutron
       Status: Incomplete => Expired

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

Title:
  [RFE] Add support for external vxlan encapsulation to neutron router

Status in neutron:
  Expired

Bug description:
  Problem Description

  In my deployment, neutron router will be connected to its upstream router with vxlan tunnel.
  But when setting neutron router gw as vxlan network, it can't work. Because there is no way to configure the vxlan peer address or vxlan multicast group.
  This configure will be also useful for other scenarios like use vxlan to connect 2 openstack directly.
  To achieve this, we propose to add a flood list to external vxlan network.

  Proposed Change

  1. CLI
  After change the CLI will looks like:
  (neutron) net-create -h
  --provider:underlay_flooding_list ip_address     Remotes IP addresses of flood list tunnel for VXLAN networks. You can repeat this option.

  2. When to create/remove tunnel
  When router-gateway-set is called, it will create a qg- interface.
  We need set "external_network_bridge" to empty, then qg- will attached to br-int. Why?
  Because br-ex did not provide vlan isolation of network.

  Then ovs agent will detect the new qg- interface, and check:
  1. qg- interface is router gw interface
  2. qg- interface' network type is vxlan
  3. qg- interface' network have flood list
  Then it will create vxlan tunnel, and add flows.
  Similar case for remove tunnel.

  3. How to create tunnel
  The flood list tunnel will be create in br-tun.

  Please help review:
  https://review.openstack.org/#/q/topic:vxlan_vteps

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