From: Dominik Csapak <d.csapak@proxmox.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>, pdm-devel@lists.proxmox.com
Subject: Re: [PATCH datacenter-manager v2 1/4] lib/api/ui: add location property to remote config
Date: Tue, 5 May 2026 10:46:40 +0200 [thread overview]
Message-ID: <9130c192-b6fd-4557-8d99-63c9fb847415@proxmox.com> (raw)
In-Reply-To: <544eb1b9-eb2f-4094-8b96-57f5f7492058@proxmox.com>
On 5/5/26 10:42 AM, Thomas Lamprecht wrote:
> Am 05.05.26 um 10:35 schrieb Dominik Csapak:
>>
>>
>> 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?
>
> exactly what I meant.
>> 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
>
> If you really want to provide those old releases this features we can port
> it back, that said, EOL is nearing for those (bit over ~3 months left), and
> especially for this non-essential feature I'd just not bother with that.
understood
>
> And why should we not show this on the PVE nodes themselves? And independent
> of that it's in anyway a property of a PVE/ node and tied to that physical
> location, not a property of a PDM remote config entry, which should IMO not
> care about these things, at least not as primary source of such information
> (overrides can be OK, but IMO not really justified here).
yeah, you're right, i'll make it part of the node config for pve/pbs
in a v3, thanks for the feedback!
next prev parent reply other threads:[~2026-05-05 8:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-05 7:31 [PATCH datacenter-manager/yew-widget-toolkit/yew-widget-toolkit-assets v2 0/8] add a new map widget for custom views Dominik Csapak
2026-05-05 7:31 ` [PATCH yew-widget-toolkit v2 1/3] js-helper: add client-to-svg-coordinate conversion helper Dominik Csapak
2026-05-05 7:31 ` [PATCH yew-widget-toolkit v2 2/3] widget: charts: add interactive Map with zoom/pan and clustering Dominik Csapak
2026-05-05 7:31 ` [PATCH yew-widget-toolkit v2 3/3] widget: charts: add WorldMap with GeoJSON rendering Dominik Csapak
2026-05-05 7:31 ` [PATCH yew-widget-toolkit-assets v2 1/1] charts: add necessary classes for Map Dominik Csapak
2026-05-05 7:31 ` [PATCH datacenter-manager v2 1/4] lib/api/ui: add location property to remote config Dominik Csapak
2026-05-05 8:26 ` Thomas Lamprecht
2026-05-05 8:36 ` Dominik Csapak
2026-05-05 8:44 ` Thomas Lamprecht
2026-05-05 8:46 ` Dominik Csapak [this message]
2026-05-05 7:31 ` [PATCH datacenter-manager v2 2/4] lib/api: add new 'remote-list' info to the resource status Dominik Csapak
2026-05-05 7:31 ` [PATCH datacenter-manager v2 3/4] ui: add world map geojson update script Dominik Csapak
2026-05-05 7:31 ` [PATCH datacenter-manager v2 4/4] ui: views: add map component Dominik Csapak
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9130c192-b6fd-4557-8d99-63c9fb847415@proxmox.com \
--to=d.csapak@proxmox.com \
--cc=pdm-devel@lists.proxmox.com \
--cc=t.lamprecht@proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox