From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id 7165A1FF140 for ; Fri, 08 May 2026 10:41:28 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 3DB9F10E44; Fri, 8 May 2026 10:41:16 +0200 (CEST) From: Dominik Csapak To: pve-devel@lists.proxmox.com, pbs-devel@lists.proxmox.com Subject: [PATCH manager 1/2] node config: add location property Date: Fri, 8 May 2026 10:40:15 +0200 Message-ID: <20260508084038.1405206-5-d.csapak@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260508084038.1405206-1-d.csapak@proxmox.com> References: <20260508084038.1405206-1-d.csapak@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL 0.050 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 URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [nodeconfig.pm] Message-ID-Hash: IYQIQ73EECYX45EBETF6KGSLZTEVJGEH X-Message-ID-Hash: IYQIQ73EECYX45EBETF6KGSLZTEVJGEH X-MailFrom: d.csapak@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox Backup Server development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: consisting of an optional name and a set of coordinates. This can be used by management systems (such as PDM) to query and display the location of a node, e.g. on a world map. It's added per node in addition to the one in the datacente config, so an admin can provide a different location per node instead of only one per cluster. Signed-off-by: Dominik Csapak --- PVE/NodeConfig.pm | 30 ++++++++++++++++++++++++++++++ 1 file changed, 30 insertions(+) diff --git a/PVE/NodeConfig.pm b/PVE/NodeConfig.pm index 87eea2a5..0ed959b7 100644 --- a/PVE/NodeConfig.pm +++ b/PVE/NodeConfig.pm @@ -186,6 +186,36 @@ $confdesc->{acme} = { optional => 1, }; +my $location_desc = { + name => { + type => 'string', + description => 'The name of the location of this node', + typetext => "", + optional => 1, + maxLength => 128, + }, + latitude => { + type => 'number', + description => "The latitude of the nodes location in degrees.", + minimum => -90, + maximum => 90, + }, + longitude => { + type => 'number', + description => "The longitude of the nodes location in degrees.", + minimum => -180, + maximum => 180, + }, +}; + +$confdesc->{location} = { + type => 'string', + format => $location_desc, + description => + "The location of the node. Overrides the default from the datacenter config.", + optional => 1, +}; + for my $i (0 .. $MAXDOMAINS) { $confdesc->{"acmedomain$i"} = { type => 'string', -- 2.47.3