storage: fixup PBS wiki link

[pve-docs.git] / pvesdn.adoc

diff --git a/pvesdn.adoc b/pvesdn.adoc
index 05547dccf4af3ffcf6b5c7fd9f70c1b613469229..c1597b82cd30e6492d4190d16fb67400f0364bbb 100644 (file)
--- a/pvesdn.adoc
+++ b/pvesdn.adoc
@@ -37,12 +37,14 @@ Basic Overview
 The {pve} SDN allows separation and fine grained control of Virtual Guests
 networks, using flexible software controlled configurations.
 
-Separation consists of zones, a zone is it's own virtual separated area.
-A Zone can be used by one or more 'VNets'. A 'VNet' is virtual network in a
-zone. Normally it shows up as a common Linux bridge with either a VLAN or
-'VXLAN' tag, or using layer 3 routing for control.
-The 'VNets' are deployed locally on each node, after configuration was commited
-from the cluster wide datacenter level.
+Separation consists of zones, a zone is it's own virtual separated network area.
+A 'VNet' is a type of a virtual network connected to a zone. Depending on which
+type or plugin the zone uses it can behave differently and offer different
+features, advantages or disadvantages.
+Normally a 'VNet' shows up as a common Linux bridge with either a VLAN or
+'VXLAN' tag, but some can also use layer 3 routing for control.
+The 'VNets' are deployed locally on each node, after configuration was committed
+from the cluster wide datacenter SDN administration interface.
 
 
 Main configuration
@@ -60,7 +62,7 @@ On the web-interface  SDN feature have 4 main sections for the configuration
 
 * VNets: The per-node building block to provide a Zone for VMs
 
-* Controller: 
+* Controller: For complex setups to control Layer 3 routing
 
 
 [[pvesdn_config_main_sdn]]
@@ -112,6 +114,9 @@ VNet properties are:
 
 * Tag: The unique VLAN or VXLAN id
 
+* VLAN Aware: Allow to add an extra VLAN tag in the virtual machine or
+  container vNIC configurations or allow the guest OS to manage the VLAN's tag.
+
 * IPv4: an anycast IPv4 address, it will be configured on the underlying bridge
   on each node part of the Zone. It's only useful for `bgp-evpn` routing.
 
@@ -148,7 +153,7 @@ specific VNets VLAN tag, and restrict Virtual Machines to separated zones.
 
 Specific `VLAN` configuration options:
 
-bridge:: Reuse this local VLAN-aware bridge, or OVS interface, already
+bridge:: Reuse this local bridge or OVS switch, already
 configured on *each* local node.
 
 [[pvesdn_zone_plugin_qinq]]
@@ -158,7 +163,7 @@ QinQ Zones
 QinQ is stacked VLAN. The first VLAN tag defined for the zone
 (so called 'service-vlan'), and the second VLAN tag defined for the vnets
 
-NOTE: Your physical network switchs must support stacked VLANs!
+NOTE: Your physical network switches must support stacked VLANs!
 
 Specific QinQ configuration options:
 
@@ -220,6 +225,8 @@ lower than the outgoing physical interface.
 Controllers Plugins
 -------------------
 
+For complex zones requiring a control plane.
+
 [[pvesdn_controller_plugin_evpn]]
 EVPN Controller
 ~~~~~~~~~~~~~~~
@@ -261,6 +268,12 @@ After applying the configuration through the main SDN web-interface panel,
 the local network configuration is generated locally on each node in
 `/etc/network/interfaces.d/sdn`, and with ifupdown2 reloaded.
 
+You need to add
+----
+source /etc/network/interfaces.d/*
+----
+at the end of /etc/network/interfaces to have the sdn config included
+
 You can monitor the status of local zones and vnets through the main tree.
 
 
@@ -427,7 +440,7 @@ Create a `myvnet2' with customer VLAN-id 100 on the previously created
 
 ----
 id: myvnet2
-zone: qinqzone1
+zone: qinqzone2
 tag: 100
 ----
 
@@ -659,7 +672,7 @@ id: myvnet1
 zone: myevpnzone
 tag: 11000
 ipv4: 10.0.1.1/24
-mac address: 8C:73:B2:7B:F9:60 #random generate mac addres
+mac address: 8C:73:B2:7B:F9:60 #random generate mac address
 ----
 
 Create the second VNet named `myvnet2' using the same EVPN zone `myevpnzone', a