Feature #2574

Bridge Configuration/physical device attach in VLAN driver on existing bridge

Added by Jaime Melis almost 6 years ago. Updated over 5 years ago.

Status:ClosedStart date:12/18/2013
Priority:NormalDue date:
Assignee:Jaime Melis% Done:

0%

Category:Drivers - Network
Target version:Release 4.6
Resolution:wontfix Pull request:

Description

Evaluate the inclusion of the attached patch contributed by Michael Kutzner

(from http://lists.opennebula.org/pipermail/users-opennebula.org/2013-December/025911.html)

diff.8021q_bridge (1.42 KB) Jaime Melis, 12/18/2013 03:29 PM

History

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

  • Parent task set to #2573

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

  • Target version changed from Release 4.6 to Release 4.4

#3 Updated by Ruben S. Montero almost 6 years ago

  • Parent task deleted (#2573)

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

  • Target version changed from Release 4.4 to Release 4.6

#5 Updated by Jaime Melis over 5 years ago

  • Status changed from New to Closed
  • Resolution set to wontfix

Hi Michael,

I'm not sure I follow, actually. As far as I can tell, the scenario you are describing happens if you specify the bridge's name, instead of letting OpenNebula decide. In other words, in your particular case, you should specify PHY_DEV but not BRIDGE, and OpenNebula will generate a onebrX bridge and attach the tagged eth1.X interface to that bridge, resulting in:

+-----------+ +----------+
|  br10     | | onebrX   |
+-----+-----+ +-----+----+
      |             |
      |             |
+-----+-----+ +-----+----+
|   eth0    | |  eth1.X  |
+-----------+ +----------+

instead of having both eth0 and eth1 in br10. Does this make sense?

I'm closing the ticket for the moment, but feel free to reopen it if this doesn't make sense.

Also available in: Atom PDF