From: Alexandre Derumier <aderumier@odiso.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH v2 pve-docs 1/2] sdn: add simple zone plugin documentation
Date: Fri, 28 Aug 2020 14:40:16 +0200 [thread overview]
Message-ID: <20200828124017.11746-2-aderumier@odiso.com> (raw)
In-Reply-To: <20200828124017.11746-1-aderumier@odiso.com>
---
pvesdn.adoc | 14 ++++++++++++--
1 file changed, 12 insertions(+), 2 deletions(-)
diff --git a/pvesdn.adoc b/pvesdn.adoc
index c1597b8..ed8652d 100644
--- a/pvesdn.adoc
+++ b/pvesdn.adoc
@@ -142,12 +142,22 @@ Common options
nodes:: Deploy and allow to use a VNets configured for this Zone only on these
nodes.
+[[pvesdn_zone_plugin_simple]]
+Simple Zones
+~~~~~~~~~~~~
+
+This is the simplest plugin, it will create an isolated vnet bridge.
+This bridge is not linked to physical interfaces, VM traffic is only
+local to the node(s).
+It can be used for NAT or routed setup.
+
+
[[pvesdn_zone_plugin_vlan]]
VLAN Zones
~~~~~~~~~~
-This is the simplest plugin, it will reuse an existing local Linux or OVS
-bridge, and manage VLANs on it.
+This plugin will reuse an existing local Linux or OVS bridge,
+and manage VLANs on it.
The benefit of using SDN module, is that you can create different zones with
specific VNets VLAN tag, and restrict Virtual Machines to separated zones.
--
2.20.1
next prev parent reply other threads:[~2020-08-28 12:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-28 12:40 [pve-devel] [PATCH v2 pve-docs 0/2] simple zone + subnet/ipam documentation Alexandre Derumier
2020-08-28 12:40 ` Alexandre Derumier [this message]
2020-08-28 12:40 ` [pve-devel] [PATCH v2 pve-docs 2/2] sdn : add " Alexandre Derumier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200828124017.11746-2-aderumier@odiso.com \
--to=aderumier@odiso.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox