yahoo-eng-team team mailing list archive

[Kevin Benton <1683256@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

The way the Linux Bridge multinode job works right now, the VXLAN tenant
networks are not using l2_population and subsequently rely on the
multicast 'group' feature of kernel bridges for carrying broadcast
traffic.

This would not normally be a problem, however, the local interface they
are using to send this multicast traffic is the one attached directly to
the provider cloud's network. So we are ultimately at the mercy of the
provider's networks to carry multicast traffic between the multi-node
instances, which is just asking for failures.

We need to adjust the job to setup a tunnel between the multinode
instances to safely carry traffic between them like we do for DVR [1].

1. https://git.openstack.org/cgit/openstack-infra/devstack-gate/tree
/devstack-vm-gate.sh#n149

This is likely leading to the instability of the LB multi-node job when
the job is on certain cloud providers that might not have good multicast
routing.

** Affects: neutron
     Importance: Critical
         Status: New


** Tags: gate-failure

** Tags added: gate-failure

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

** Description changed:

  The way the Linux Bridge multinode job works right now, the VXLAN tenant
  networks are not using l2_population and subsequently rely on the
  multicast 'group' feature of kernel bridges for carrying broadcast
  traffic.
  
  This would not normally be a problem, however, the local interface they
  are using to send this multicast traffic is the one attached directly to
  the provider cloud's network. So we are ultimately at the mercy of the
  provider's networks to carry multicast traffic between the multi-node
  instances, which is just asking for failures.
  
  We need to adjust the job to setup a tunnel between the multinode
  instances to safely carry traffic between them like we do for DVR [1].
  
- 1. http://git.openstack.org/cgit/openstack-infra/devstack-
- gate/tree/multinode_setup_info.txt
+ 1. https://git.openstack.org/cgit/openstack-infra/devstack-gate/tree
+ /devstack-vm-gate.sh#n149
  
- 
- This is likely leading to the instability of the LB multi-node job when the job is on certain cloud providers that might not have good multicast routing.
+ This is likely leading to the instability of the LB multi-node job when
+ the job is on certain cloud providers that might not have good multicast
+ routing.

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

Title:
  linuxbridge multinode depending on multicast support of provider

Status in neutron:
  New

Bug description:
  The way the Linux Bridge multinode job works right now, the VXLAN
  tenant networks are not using l2_population and subsequently rely on
  the multicast 'group' feature of kernel bridges for carrying broadcast
  traffic.

  This would not normally be a problem, however, the local interface
  they are using to send this multicast traffic is the one attached
  directly to the provider cloud's network. So we are ultimately at the
  mercy of the provider's networks to carry multicast traffic between
  the multi-node instances, which is just asking for failures.

  We need to adjust the job to setup a tunnel between the multinode
  instances to safely carry traffic between them like we do for DVR [1].

  1. https://git.openstack.org/cgit/openstack-infra/devstack-gate/tree
  /devstack-vm-gate.sh#n149

  This is likely leading to the instability of the LB multi-node job
  when the job is on certain cloud providers that might not have good
  multicast routing.

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