From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <s.lendl@proxmox.com> Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id C12589A868 for <pve-devel@lists.proxmox.com>; Fri, 17 Nov 2023 14:56:07 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id A0C5433DCC for <pve-devel@lists.proxmox.com>; Fri, 17 Nov 2023 14:55:37 +0100 (CET) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [94.136.29.106]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS for <pve-devel@lists.proxmox.com>; Fri, 17 Nov 2023 14:55:37 +0100 (CET) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id E797143E4E for <pve-devel@lists.proxmox.com>; Fri, 17 Nov 2023 14:55:36 +0100 (CET) From: Stefan Lendl <s.lendl@proxmox.com> To: pve-devel@lists.proxmox.com Date: Fri, 17 Nov 2023 14:55:28 +0100 Message-ID: <20231117135531.3198353-4-s.lendl@proxmox.com> X-Mailer: git-send-email 2.42.0 In-Reply-To: <20231117135531.3198353-1-s.lendl@proxmox.com> References: <20231117135531.3198353-1-s.lendl@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL 0.068 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record T_SCC_BODY_TEXT_LINE -0.01 - Subject: [pve-devel] [PATCH v2 pve-docs 3/6] sdn: VNets and Subnets X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion <pve-devel.lists.proxmox.com> List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-devel>, <mailto:pve-devel-request@lists.proxmox.com?subject=unsubscribe> List-Archive: <http://lists.proxmox.com/pipermail/pve-devel/> List-Post: <mailto:pve-devel@lists.proxmox.com> List-Help: <mailto:pve-devel-request@lists.proxmox.com?subject=help> List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel>, <mailto:pve-devel-request@lists.proxmox.com?subject=subscribe> X-List-Received-Date: Fri, 17 Nov 2023 13:56:07 -0000 Signed-off-by: Stefan Lendl <s.lendl@proxmox.com> --- pvesdn.adoc | 46 ++++++++++++++++++++++++++++------------------ 1 file changed, 28 insertions(+), 18 deletions(-) diff --git a/pvesdn.adoc b/pvesdn.adoc index 8a71c03..c4b77f0 100644 --- a/pvesdn.adoc +++ b/pvesdn.adoc @@ -272,32 +272,40 @@ MTU:: Because VXLAN encapsulation uses 50 bytes, the MTU needs to be 50 bytes defaults to 1450. -[[pvesdn_config_vnet]] +[[pvesdn_config_vnets]] VNets ------ +------------- + +After creating a virtual network (VNet) through the SDN GUI, a local network +interface with the same name is available on each node. To connect a guest to the +VNet, assign the interface to the guest and set the IP address accordingly. + +Depending on the zone, these options have different meanings and are explained +in the respective zone section in this document. -A `VNet` is, in its basic form, a Linux bridge that will be deployed locally on -the node and used for virtual machine communication. +WARNING: In the current state, some options may have no effect or won't work in +certain zones. -The VNet configuration properties are: +VNet configuration options: -ID:: An 8 character ID to name and identify a VNet +ID:: An up to 8 character ID to identify a VNet -Alias:: Optional longer name, if the ID isn't enough +Comment:: More descriptive identifier. Assigned as an alias on the interface. Optional Zone:: The associated zone for this VNet Tag:: The unique VLAN or VXLAN ID -VLAN Aware:: Enable adding an extra VLAN tag in the virtual machine or -container's vNIC configuration, to allow the guest OS to manage the VLAN's tag. +VLAN Aware:: Enables vlan-aware option on the interface, enabling configuration + in the quest. + [[pvesdn_config_subnet]] Subnets -~~~~~~~~ +------------- -A subnetwork (subnet) allows you to define a specific IP network -(IPv4 or IPv6). For each VNet, you can define one or more subnets. +A subnet define a specific IP range, described by the CIDR network address. +Each VNet, can have one or more subnets. A subnet can be used to: @@ -310,19 +318,21 @@ A subnet can be used to: If an IPAM server is associated with the subnet zone, the subnet prefix will be automatically registered in the IPAM. -Subnet properties are: +Subnet configuration options: ID:: A CIDR network address, for example 10.0.0.0/8 Gateway:: The IP address of the network's default gateway. On layer 3 zones (Simple/EVPN plugins), it will be deployed on the VNet. -SNAT:: Optional. Enable SNAT for layer 3 zones (Simple/EVPN plugins), for this - subnet. The subnet's source IP will be NATted to server's outgoing interface/IP. - On EVPN zones, this is only done on EVPN gateway-nodes. +SNAT:: Enable Source NAT which allows VMs from inside a + VNet to connect to the outside network by forwarding the packets to the nodes + outgoing interface. On EVPN zones, forwarding is done on EVPN gateway-nodes. + Optional. + +DNS Zone Prefix:: Add a prefix to the domain registration, like + <hostname>.prefix.<domain> Optional. -Dnszoneprefix:: Optional. Add a prefix to the domain registration, like -<hostname>.prefix.<domain> [[pvesdn_config_controllers]] Controllers -- 2.42.0