From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id 3C7401FF179 for ; Wed, 12 Nov 2025 22:16:59 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id C4DACD94D; Wed, 12 Nov 2025 22:17:43 +0100 (CET) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com, Stefan Hanreich Date: Wed, 12 Nov 2025 22:17:28 +0100 Message-ID: <176298224761.1520762.4280069113975469612.b4-ty@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20251107143201.689035-7-s.hanreich@proxmox.com> References: <20251107143201.689035-1-s.hanreich@proxmox.com> <20251107143201.689035-7-s.hanreich@proxmox.com> MIME-Version: 1.0 X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1762982234805 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.024 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 Subject: [pve-devel] applied: [PATCH proxmox-ve-rs v3 4/7] ve-config: add optional tag property to vnet X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox VE development discussion Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" On Fri, 07 Nov 2025 15:31:20 +0100, Stefan Hanreich wrote: > When parsing the vnet.cfg config file we also want to get the tag > (vni or vlan). We need this so that we can lookup the vni of the passed > vnet on the status api call. We need the vni so that we can filter the > frr output. > > In the future we would probably want to do this better with an enum per > vnet type and parse all possible options. > > [...] Applied, thanks! [4/7] ve-config: add optional tag property to vnet commit: 899ad0970a26d127b402205e256a22d610707d24 _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel