[ovs-discuss] Problem with OpenVswitch 1.0.0 database backend and persistent settings.

Mark Persohn Mark.Persohn at superchoice.com.au
Mon May 24 03:30:24 UTC 2010


Hi Dan,
 
Thanks for that, yes I agree that a script can be used.  I guess what I was getting at was with the libvirt/qemu.xml file set to bridge and the a network interface name defined.  
<interface type='bridge'>
      <mac address='54:52:00:5f:a8:72'/>
      <source bridge='brovs1'/>
      <target dev='netwin0'/>
</interface>
 
  bridge.brovs1.port=bond1
  bridge.brovs1.port=brovs1
  vlan.brovs1.trunk=4
  vlan.brovs1.trunk=5
  vlan.brovs1.trunk=6
  vlan.netwin0.tag=6
Everything just worked with OpenVswitch 0.90.7.  No external scripts/glue required.  Start the VM it world 'bridge' to the OpenVswitch and with the VLAN access predefined the traffic would flow.
Is there any chance of having OpenVswitch save Port configuration in the database?  That way when the port is initialized the config would be applied?
 
Thanks again..  I guess I'm off to have a look at the INSTALL.KVM
 
Cheers
 
Mark
 
 
 
 


>>> Dan Wendlandt <dan at nicira.com> 22/05/2010 06:02 >>>


On Thu, May 20, 2010 at 1:47 AM, Mark Persohn <Mark.Persohn at superchoice.com.au> wrote:



I have looked at trying to run a script as prt of the VM startup but since we are running libvirtd/qemu in bridge
mode it will not run scripts! 

I do not have any hands-on experience with libvirt and KVM, but from talking to other people who have used OVS with libvirt, I was under the impression that libvirt provides a mechanism by which you can bring up VM interface devices using an arbitrary script. 

The libvirt docs (http://libvirt.org/formatdomain.html#elementsNICSEthernet ( http://libvirt.org/formatdomain.html#elementsNICSEthernet ) ) mention: 


Generic ethernet connection
Provides a means for the administrator to execute an arbitrary script to connect the guest's network to the LAN. The guest will have a tun device created with a name of vnetN, which can also be overridden with the <target> element. After creating the tun device a shell script will be run which is expected to do whatever host network integration is required. By default this script is called /etc/qemu-ifup but can be overridden....
<devices>
<interface type='ethernet'/>
...
<interface type='ethernet'>
<target dev='vnet7'/>
<script path='/etc/qemu-ifup-mynet'/>
</interface>
</devices>
...
I am guessing such a script might let you override libvirt's mechanism for adding a VM interface device to the bridge and instead let you directly configure it using OVS (e.g., ovs-vsctl set port netwin0 tag=6 ). 

As I recall, you're not the first person to have this problem so however we end up resolving it, we should document this better on the OVS site.

dan






The old conf file mode made running VM's with libvirtd/qemu very easy/elegant.
Do I have any options to get this working with 1.0.0?

Thanks in advance.

Mark









Please consider the environment before you print this email
For email conditions, please see our website http://www.superchoice.com.au/email_conditions.htm 

_______________________________________________
discuss mailing list
discuss at openvswitch.org 
http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org 


!DSPAM:4bf6c5a5113018859040696! 




Please consider the environment before you print this email
For email conditions, please see our website  http://www.superchoice.com.au/email_conditions.htm
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openvswitch.org/pipermail/ovs-discuss/attachments/20100524/8f463ef4/attachment-0001.html>


More information about the discuss mailing list