From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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 1B2399B559 for ; Mon, 20 Nov 2023 17:29:09 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id F251B1CD34 for ; Mon, 20 Nov 2023 17:28:38 +0100 (CET) Received: from lana.proxmox.com (unknown [94.136.29.99]) by firstgate.proxmox.com (Proxmox) with ESMTP for ; Mon, 20 Nov 2023 17:28:38 +0100 (CET) Received: by lana.proxmox.com (Postfix, from userid 10043) id 2A3162C2513; Mon, 20 Nov 2023 17:28:38 +0100 (CET) From: Stefan Hanreich To: pve-devel@lists.proxmox.com Date: Mon, 20 Nov 2023 17:28:31 +0100 Message-Id: <20231120162833.431139-1-s.hanreich@proxmox.com> X-Mailer: git-send-email 2.39.2 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL -0.625 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 KAM_LAZY_DOMAIN_SECURITY 1 Sending domain does not have any anti-forgery methods POISEN_SPAM_PILL 0.1 Meta: its spam POISEN_SPAM_PILL_1 0.1 random spam to be learned in bayes POISEN_SPAM_PILL_3 0.1 random spam to be learned in bayes RDNS_NONE 0.793 Delivered to internal network by a host with no rDNS SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_NONE 0.001 SPF: sender does not publish an SPF Record T_SCC_BODY_TEXT_LINE -0.01 - Subject: [pve-devel] [PATCH network/manager 0/2] Refactor IPAM API methods 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: , X-List-Received-Date: Mon, 20 Nov 2023 16:29:09 -0000 Moving the API method for the IPAM index to /ipams/pve/status which seems better suited as it returns the current state of the PVE IPAM. This could be then extended further to return the current status of other IPAM plugins, although it is probably preferrable to use the respective API / UI of the IPAM for retrieving its current status rather than using the PVE API. Additionally moved the IPAM Mapping create / update / delete endpoints to /vnets/{vnetid}/ips since they are part of the VNet and those methods not only manage IPAM related state but also stuff like DNS plugin state. Currently I did not add a links relation to the endpoint, since there is no GET endpoint that would retrieve a single mapping from the API. I did not find any other relations present in our current API. If we move to displaying the state of the IPAM to the Zone panel, then we could move the Index as well as the create / update / delete methods to the Zone endpoint and then it would be possible to show a proper child relation. pve-network: Stefan Hanreich (1): api: refactor URL structure for Ipam src/PVE/API2/Network/SDN.pm | 6 -- src/PVE/API2/Network/SDN/Ipams.pm | 83 +++++++++++++++++ src/PVE/API2/Network/SDN/{Ipam.pm => Ips.pm} | 97 ++------------------ src/PVE/API2/Network/SDN/Makefile | 2 +- src/PVE/API2/Network/SDN/Vnets.pm | 6 ++ 5 files changed, 100 insertions(+), 94 deletions(-) rename src/PVE/API2/Network/SDN/{Ipam.pm => Ips.pm} (58%) pve-manager: Stefan Hanreich (1): sdn: Update IPAM API endpoints www/manager6/sdn/IpamEdit.js | 4 +++- www/manager6/tree/DhcpTree.js | 15 +++++++++++---- 2 files changed, 14 insertions(+), 5 deletions(-) Summary over all repositories: 7 files changed, 114 insertions(+), 99 deletions(-) -- murpp v0.4.0