Differences

This shows you the differences between two versions of the page.

--- hypervisor:base:network [2015/03/04 22:40]
admin [Initial Networking Configuration]
+++ hypervisor:base:network [2015/03/04 22:44]
admin [Open vSwitch]
@@ Line 25: / Line 25: @@
 All supported VLAN configurations are equally applicable to pools and standalone hosts, and bonded and non-bonded configurations.
-----
 ----
 =====  Initial Networking Configuration =====
@@ Line 103: / Line 101: @@
 {{ :hypervisor:base:network:network-bridge.png?direct&200 |}}
+----
-=== Setting up bridged networking ===
-The recommended method for configuring bridged networking is to use your distro supplied network configuration tools as described in [[http://wiki.xenproject.org/wiki/Host_Configuration/Networking|Host Configuration/Networking]].
-The XL toolstack will never modify the network configuration and expects that the administrator will have configured the host networking appropriately.
-=== Attaching virtual devices to the appropriate bridge ===
-When a domU starts up the vif-bridge script is run which:
-    attaches vifDOMID.DEVID to the appropriate bridge
-    brings vifDOMID.DEVID up.
-With XL and xend the bridge to us for each VIF can be configured using the bridge configuration key. e.g.
-<code>
-   vif=[ 'bridge=mybridge' ]
-</code>
-or
-<code>
-   vif=[ 'mac=00:16:3e:01:01:01,bridge=mybridge' ]
-</code>
-or to create multiple interfaces attached to different bridges:
-<code>
-   vif=[ 'mac=00:16:3e:70:01:01,bridge=br0', 'mac=00:16:3e:70:02:01,bridge=br1' ]
-</code>
 ==== Open vSwitch ====
+----
 The Xen 4.3 release will feature initial integration of [[http://www.openvswitch.org/|Open vSwitch]] based networking. Conceptually this is similar to a bridged configuration but rather than placing each vif on a Linux bridge instead an Open vSwitch switch is used. Open vSwitch supports more advanced [[http://en.wikipedia.org/wiki/Software-defined_networking|Software-defined Networking (SDN)]] features such as [[http://www.openflow.org/|OpenFlow]].
-=== Setting up Open vSwitch networking ===
-Set up openvswitch according to the [[http://wiki.xenproject.org/wiki/Network_Configuration_Examples_(Xen_4.1%2B)|Host Networking Configuration Examples]].
-If you want openvswitch to be the default, add the following line to your xl.conf file:
-<code>
-vif.default.script="vif-openvswitch"
-</code>
-If you have given the openvswitch bridge a name other than xenbr0, you will need to update that default as well:
-<code>
-vif.default.bridge="ovsbr0"
-</code>
-Alternately, you can specify the new script (and bridge, if necessary) in each config file by adding script=vif-openvswitch (and possiblybridge=ovsbr0) to the vifspec of individual vifs in config files. See xl-network-configuration.markdown for more information.
-=== Attaching virtual devices to the appropriate switch ===
-Xen 4.3 ships with a vif-openvswitch hotplug script which behaves similarly to the vif-bridge script, except that it attaches the VIF to an openvswitch switch (named via the VIF's bridge parameter).
-In addition to naming the bridge the openvswitch hotplug script supports an extended syntax for the bridge option which allows for VLAN tagging and trunking. That syntax is:
-<code>
-BRIDGE_NAME[.VLAN][:TRUNK:TRUNK]
-</code>
-To add a vif to VLAN 102 on bridge xenbr0:
-<code>
-vif = [ 'mac=00:16:3e:01:01:01,bridge=xenbr0.102' ]
-</code>
-To add a vif to bridge xenbr1 trunked and receiving traffic for VLAN 101 and 202:
-<code>
-vif = [ 'mac=00:16:3e:01:01:01,bridge=xenbr0:101:202' ]
-</code>