diff options
| author | Robby Workman <rworkman@slackbuilds.org> | 2011-04-05 21:00:27 -0500 |
|---|---|---|
| committer | Robby Workman <rworkman@slackbuilds.org> | 2011-04-05 21:00:27 -0500 |
| commit | e3e6a8e2e8aaae17ad1996b70d2bfddb295506e1 (patch) | |
| tree | 5ccac38f7132e83f89056c189500d27333713f36 /network/openvswitch/xen/README | |
| parent | eddeeef9154c8dfd895e667facbdfc32a95e7f34 (diff) | |
| download | slackbuilds-e3e6a8e2e8aaae17ad1996b70d2bfddb295506e1.tar.gz | |
network/openvswitch: Removed (build failure)
The code in upstream's git repo might build, but it's not
even in a beta status yet, so it will have to wait (but of
course the SBo maintainer is free to begin testing already)
Signed-off-by: Robby Workman <rworkman@slackbuilds.org>
Diffstat (limited to 'network/openvswitch/xen/README')
| -rw-r--r-- | network/openvswitch/xen/README | 39 |
1 files changed, 0 insertions, 39 deletions
diff --git a/network/openvswitch/xen/README b/network/openvswitch/xen/README deleted file mode 100644 index 93889615e7..0000000000 --- a/network/openvswitch/xen/README +++ /dev/null @@ -1,39 +0,0 @@ -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. |