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 41EA21FF141 for ; Tue, 05 May 2026 10:37:56 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 6F5B61DF2D; Tue, 5 May 2026 10:37:58 +0200 (CEST) Message-ID: <246ec646-b7cf-4570-88a7-089e066dc129@proxmox.com> Date: Tue, 5 May 2026 10:36:52 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Beta Subject: Re: [PATCH datacenter-manager v2 1/4] lib/api/ui: add location property to remote config To: Thomas Lamprecht , pdm-devel@lists.proxmox.com References: <20260505073203.398548-1-d.csapak@proxmox.com> <20260505073203.398548-6-d.csapak@proxmox.com> Content-Language: en-US From: Dominik Csapak In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1777970107075 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 Message-ID-Hash: CTNOX7FQXR2YPYLX46P33QIBVM3M2ZJT X-Message-ID-Hash: CTNOX7FQXR2YPYLX46P33QIBVM3M2ZJT 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 Datacenter Manager development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: On 5/5/26 10:24 AM, Thomas Lamprecht wrote: > Am 05.05.26 um 09:31 schrieb Dominik Csapak: >> this will be used to show the remote on a map in a custom view. >> Let's the user simply enter the longitude and latitude in the remote >> edit window. > > Would be nicer and more fitting to have this on the remote side, i.e. the > node configs as metadata or similar format-string field. > > And one location per remote won't cut it for PVE. We know of clusters that > are distributed over different location with a few km distance in between > and a dark fiber channel for near LAN latency to upheld cluster communication > requirements. do you mean that the user configures that on the pve and pbs side per node? if yes, sure that is doable. I didn't go this way to not exclude users with older clusters (e.g. 8.4) to use that feature. also it's metadata that the pve nodes themselves won't really use