Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
hypervisor:base:network [2015/03/04 22:43] admin [Bridging] |
hypervisor:base:network [2015/03/04 22:45] (current) admin [Beginners Network Configuration] |
||
|---|---|---|---|
| Line 101: | Line 101: | ||
| {{ :hypervisor:base:network:network-bridge.png?direct&200 |}} | {{ :hypervisor:base:network:network-bridge.png?direct&200 |}} | ||
| + | ---- | ||
| ==== Open vSwitch ==== | ==== 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]]. | 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> | ||
| - | |||
| - | |||
| - | ===== Beginners Network Configuration ===== | ||
| ==== Software Bridge ==== | ==== Software Bridge ==== | ||
