summaryrefslogtreecommitdiff
path: root/network/openvswitch/xen/README
diff options
context:
space:
mode:
authorChristopher Walker <kris240376@gmail.com>2011-03-07 12:08:14 -0300
committerNiels Horn <niels.horn@slackbuilds.org>2011-03-07 12:08:14 -0300
commit61ac3bfa4353955d6d2a2269073b460bce66838a (patch)
tree08fb2e85622c754ac03ada1f69f019dd6b87787a /network/openvswitch/xen/README
parente1f98f7da255fb536738ce5087f217695f0b84bc (diff)
downloadslackbuilds-61ac3bfa4353955d6d2a2269073b460bce66838a.tar.gz
network/openvswitch: Added (multilayer virtual switch)
Signed-off-by: Niels Horn <niels.horn@slackbuilds.org>
Diffstat (limited to 'network/openvswitch/xen/README')
-rw-r--r--network/openvswitch/xen/README39
1 files changed, 39 insertions, 0 deletions
diff --git a/network/openvswitch/xen/README b/network/openvswitch/xen/README
new file mode 100644
index 0000000000..93889615e7
--- /dev/null
+++ b/network/openvswitch/xen/README
@@ -0,0 +1,39 @@
+Here are some scripts that I've written for use with Xen at my site.
+In order to use these scripts with your Xen installation you'll need to copy
+both the network-openvswitch and vif-openvswitch files to your
+/etc/xen/scripts directory. You can instruct Xen to use these scripts by
+editing your /etc/xen/xend-config.sxp file and specifying these scripts as
+the default network-script and vif-script.
+
+For example, here are the entries in my xend-config.sxp file:
+
+ (network-script 'network-openvswitch netdev=eth2 bridge=ovs0')
+
+ (vif-script 'vif-openvswitch bridge=ovs0')
+
+If your network interface card and attached network switch support VLAN
+tagged traffic, you can place virtual machines within a seperate VLAN by
+appending a '.' and the VLAN tag number you wish the domain to use. For
+example, to have all domains default to VLAN 2 you can do the following:
+
+ (vif-script 'vif-openvswitch bridge=ovs0.2')
+
+You can also specify tagged traffic in the domain configuration file.
+
+If you are hosting a hardware virtualized domain understand that the
+/etc/xen/scripts/qemu-ifup script is run instead of the vif-script specified
+in the xend-config.sxp file. You'll need to edit this file to add the port
+to the vswitch instead of using the brctl (unless of course you are using
+the appropriate kernel module to control the vswitch using brctl.) Here is
+a snippet from my qemu-ifup to handle hardware virtualized ports:
+
+ if lsmod | grep -c openvswitch_mod 1> /dev/null && ! lsmod | grep -c brcompat_mod 1> /dev/null
+ then
+ ovs-vsctl -- --may-exist add-port $bridge $1
+ else
+ brctl addif $bridge $1 || true
+ fi
+
+This doesn't handle tagged traffic. I'll leave that as an exercise for you.
+
+Enjoy.