Feature #4043

Add Time To Live (TTL) option to VXLAN driver

Added by Stefan Kooman almost 4 years ago. Updated almost 4 years ago.

Status:ClosedStart date:10/08/2015
Priority:NormalDue date:
Assignee:Ruben S. Montero% Done:

0%

Category:Drivers - Network
Target version:Release 4.14.2
Resolution:fixed Pull request:

Description

Currently OpenNebula assumes a L2 connected multicast network for VXLAN to work (same broadcast domain). But if you want to use routed multicast traffic the vxlan ttl should be > than 1 or otherwise the traffic will be dropped at the hypervisor. I changed /var/lib/one/remotes/vnm/vxlan/vxlan_driver.rbto hard code a ttl (10):

- " #{mtu} type vxlan id #{@nic[:vlan_id]} group #{mcs}"\
+ " #{mtu} type vxlan id #{@nic[:vlan_id]} group #{mcs} ttl 10"\

Ideally the ttl would be made a VXLAN option in /var/lib/one/remotes/vnm/OpenNebulaNetwork.conf, i.e.:

  1. Time To Live (TTL) for VXLAN networks. TTL should be > 1 in routed multicast networks (IGMP)
    :vxlan_ttl: 10

Associated revisions

Revision 31d26e05
Added by Ruben S. Montero almost 4 years ago

feature #4043: Support TTL for VXLAN driver

Revision e335542e
Added by Ruben S. Montero almost 4 years ago

feature #4043: Support TTL for VXLAN driver

(cherry picked from commit 31d26e05367eb208d1a18ed102e8fa915048bc45)

History

#1 Updated by Ruben S. Montero almost 4 years ago

  • Category set to Drivers - Network
  • Status changed from Pending to Assigned
  • Assignee set to Ruben S. Montero
  • Target version set to Release 4.14.2

#2 Updated by Ruben S. Montero almost 4 years ago

  • Status changed from Assigned to Closed
  • Resolution set to fixed

Thanks Stephan, implemented as proposed :). It is now ready for 4.14.2

Also available in: Atom PDF