Feature #476
Add OpenVSwitch management
Status: | Closed | Start date: | 01/30/2011 | |
---|---|---|---|---|
Priority: | High | Due date: | ||
Assignee: | Jaime Melis | % Done: | 0% | |
Category: | - | |||
Target version: | Release 3.0 | |||
Resolution: | fixed | Pull request: |
Description
Hello
Did you consider adding OpenVSwitch management to OpenNebula features?
Linux bridge works fine but a multi-server network virtualization layer managed but OpenNebula would that would ease and secure virtual machine (and services) deployment and administration.
For a comparison of OpenVSwitch and linux bridging:
http://openvswitch.org/cgi-bin/gitweb.cgi?p=openvswitch;a=blob_plain;f=WHY-OVS;h=ac9a3815a1a00ca3ad024bfb7d6652a040de8899;hb=HEAD
Thanks for your excellent work and investment to produce this quality software!
Patrice
Associated revisions
feature #476: draft of vlan hook
feature #476: abstraction class for network management in hooks
feature #476: draft of vlan hook
feature #476: abstraction class for network management in hooks
feature #476: new tester for the networking hooks
feature #476: refactor NIC classes
feature #476: adapt rspec to refactorization
feature #476: Implement ebtables and openvswitch hook
feature #476: refactor tester and implement openvswitch test in kvm
feature #476: use modules to extend main class
feature #476: possibility to specify filtered bridges in ebtables.
feature #476: vm class to obtain vm attributes
feature #476: firewall hook and class
feature #476: iptables rules now filter physdev-out. Handle established connections.
feature #476: fix typo in vlan tagging command
feature #476: get hook_location from scripts_remote_dir
feature #476: support phydev attribute in core
feature #476: unit testing for the phydev attribute in the core
feature #476: new hook trigger on PROLOG
feature #476: install hooks under remotes and place the source the under vnm_mad
feature #476: move spec files to vnm_mad
feature #476: minor refactor
feature #476: get_tap method for xen
feature #476: correct path for lsmod
feature #476: fix multiple bugs in XenVLAN.rb
feature #476: fix crash if network hooks are executed on prolog
feature #476: correct paths for commands
feature #476: apply hm hook only for NICs with phydev attributes
feature #476: xen-firewall test
feature #476: update oned.conf to reflect the new networking hooks
feature #476: banners
feature #476: refactor network classes
feature #476: rename nic class file
feature #476: update install.sh
feature #476: move all methods handling VM info to the VM class
feature #476: add filter nics test
feature #476: removed debug methods
feature #476: remove old vlan hook
feature #476: make hypervisor available to the network hooks
feature #476: Bug initializing OpenNebulaNetwork class
feature #476: Some formatting and comments
feature #476: Moved some methods to VM class
feature #476: Rename spec dir to test
feature #476: fix tests for new dir name
feature #476. Fixes tests after merge. hook_location is now inititlized
feature #476: set device up in host-managed vlan hook. Plus tests.
feature #476: fix bug in HostManaged networking hook
feature #476: add some necessary files for testing
feature #476: captura iptables commands during testing
feature #476: capture more commands during testing
feature #476: set bridge as UP after creating it
Solved wrong comments in .yaml (#476)
Solved wrong comments in .yaml (#476)
(cherry picked from commit 41b52340af7b6289651f78347a794258462957c0)
History
#1 Updated by Ruben S. Montero over 10 years ago
Hi Patrice,
We've been looking into this... IMHO the basic configuration of OpenVStiwch should be supported out-ofthe box by OpenNebula. I am thinking of the configuration described here:
http://openvswitch.org/?page_id=146
However I am not an expert in OpenVSwitch and I am probably missing something. Could you elaborate a bit what are you missing from OpenNebula?
Cheers
#2 Updated by Ruben S. Montero about 10 years ago
- Assignee set to Jaime Melis
- Target version set to Release 3.0
#3 Updated by Ruben S. Montero about 10 years ago
- Tracker changed from Request to Feature
#4 Updated by Shi Jin about 10 years ago
Hi there,
I found that on RHEL-6.1, the vlan device and the bridge device are in the DOWN state when they are created automatically by the hm-vlan hook.
I tracked it down to the ifup function in $ONE_LOCATION/var/remotes/hooks/vnm/HostManaged.rb where the ip command is called. There is a "link" word missing.
The patch is
*** HostManaged.rb 2011-07-04 15:42:11.752812304 -0600 --- /vrstorm/cloudadmin//src/onegit/src/vnm_mad/HostManaged.rb 2011-06-28 13:18:35.918490645 -0600 *************** *** 83,88 **** def ifup(dev, vlan=nil) dev = "#{dev}.#{vlan}" if vlan ! system("#{COMMANDS[:ip]} link set #{dev} up") end end --- 83,88 ---- def ifup(dev, vlan=nil) dev = "#{dev}.#{vlan}" if vlan ! system("#{COMMANDS[:ip]} set #{dev} up") end end
Please let me know if it makes sense.
Shi
#5 Updated by Jaime Melis about 10 years ago
Thanks Shi Jin for reporting that bug. Your patch has been applied.
#6 Updated by Shi Jin about 10 years ago
Hi, in fact there is another patch needed to bring up the newly created bridge device.
*** HostManaged.rb 2011-07-05 13:11:40.826802922 -0600 --- /vrstorm/cloudadmin//src/onegit/src/vnm_mad/HostManaged.rb 2011-07-05 08:29:26.624162299 -0600 *************** *** 42,48 **** if !attached_bridge_dev?(bridge, dev, vlan) attach_brigde_dev(bridge, dev, vlan) - ifup(bridge) end end end --- 42,47 ----
#7 Updated by Jaime Melis about 10 years ago
That's right Shi Jin. Patch applied. Thanks for testing it.
#8 Updated by Ruben S. Montero almost 10 years ago
- Status changed from New to Closed
- Resolution set to fixed
Support is included in OpenNebula 3.0