public inbox for pdm-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: "Lukas Wagner" <l.wagner@proxmox.com>
To: "Thomas Lamprecht" <t.lamprecht@proxmox.com>,
	"Lukas Wagner" <l.wagner@proxmox.com>,
	"Proxmox Datacenter Manager development discussion"
	<pdm-devel@lists.proxmox.com>
Subject: Re: [pdm-devel] [PATCH datacenter-manager v2 11/13] ui: add remote update view
Date: Thu, 23 Oct 2025 15:01:49 +0200	[thread overview]
Message-ID: <DDPPZDYQO4HV.2R50SHMKANKEZ@proxmox.com> (raw)
In-Reply-To: <806d934f-c128-4fe3-a073-4a4397e5c692@proxmox.com>

On Thu Oct 23, 2025 at 10:36 AM CEST, Thomas Lamprecht wrote:
> I'd mostly use "Some" and "All" to differentiate different update levels
> and show the unavailability of nodes separately. I will seldomly care how
> many nodes got updates available, only if all is OK (all up-do-date) or
> some need to be updated soon (at least one not up-do-date).
> Same for repo status.
>
> If you want to show numbers the total number count needs to be included to
> make it actually telling, like
>
> "{count} out of {total} nodes have pending updates"
>
> It might be also a good option to use three dedicated columns here, the
> (some) node unknown status could be in the front with the type icon, the
> repo status a dedicated column and the update status too.

Stayed with the same column count as before in v3, but I might
reevaluate the idea when I add the repo status warnings.

>
>
>> For a collapsed tree item that represents the entire remote, it's pretty
>> hard to 'summarise' everything into a single line in text form and still
>> fit the view, and that is why I went with the status icons plus the
>> number of nodes that have the given status.
>
> I mean, the most complex one probably would be:
>
> "{count} out of {total} nodes have pending updates, {unknown} could not be reached"
>
> Which seems still OK to me to have here.
>
> As in: you do not need to always show every possible status. We want to
> put attention on potential problems and easily show if all is OK, not
> always include all potential details, that's not that helpful when managing
> many remotes/nodes.
>
>

For v3 [1], I now added text similar as you proposed, but went with
"Some"/"All" instead of exact counts, e.g.
  - All nodes up-to-date
  - Some nodes have pending updates
  - ...

[1] https://lore.proxmox.com/pdm-devel/20251023124420.244585-1-l.wagner@proxmox.com/T/#t

> Some additional ideas that might not be that hard to already include now
> (as in: as follow-up still for 1.0, not necessarily this series)
>
> Show also the main version of the node, like the one we show at the top
> of the web UI.
>
> We could also show a summary card or the like on top with the overall
> counters, like:
>
> X nodes do not have a valid repo setup
> Y nodes have updates pending
> Z nodes are up-do-date
> A nodes run an old-stable release.
> B nodes run an End-of-Support release.
>
>
> Filters might be also nice to have from the get go, so that, e.g., one can
> only list nodes that have updates pending, which can be great in complex
> setups. Albeit, if we do the views dynamic we could even handle these things
> there and create a "Nodes with Pending Updates or Problematic Repos" view.
> So this one is one could be solved on another level than in-line, but could
> be also fine to have both – just wanted to put the idea out there, it's IMO
> something that would be quite nice to have for PDM users caring about their
> systems running up-do-date.
>

Noted for follow-ups! Thanks for the ideas!




_______________________________________________
pdm-devel mailing list
pdm-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pdm-devel

  reply	other threads:[~2025-10-23 13:01 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-17 12:09 [pdm-devel] [PATCH datacenter-manager v2 00/13] add global " Lukas Wagner
2025-10-17 12:09 ` [pdm-devel] [PATCH datacenter-manager v2 01/13] metric collection task: tests: add missing parameter for cluster_metric_export Lukas Wagner
2025-10-21 19:24   ` [pdm-devel] applied: " Thomas Lamprecht
2025-10-17 12:09 ` [pdm-devel] [PATCH datacenter-manager v2 02/13] pdm-api-types: add types for remote upgrade summary Lukas Wagner
2025-10-17 12:09 ` [pdm-devel] [PATCH datacenter-manager v2 03/13] remote updates: add cache for remote update availability Lukas Wagner
2025-10-17 12:10 ` [pdm-devel] [PATCH datacenter-manager v2 04/13] api: add API for retrieving/refreshing the remote update summary Lukas Wagner
2025-10-17 12:10 ` [pdm-devel] [PATCH datacenter-manager v2 05/13] unprivileged api daemon: tasks: add remote update refresh task Lukas Wagner
2025-10-17 12:10 ` [pdm-devel] [PATCH datacenter-manager v2 06/13] pdm-client: add API methods for remote update summaries Lukas Wagner
2025-10-17 12:10 ` [pdm-devel] [PATCH datacenter-manager v2 07/13] pbs-client: add bindings for APT-related API calls Lukas Wagner
2025-10-17 12:10 ` [pdm-devel] [PATCH datacenter-manager v2 08/13] task cache: use separate functions for tracking PVE and PBS tasks Lukas Wagner
2025-10-17 12:10 ` [pdm-devel] [PATCH datacenter-manager v2 09/13] remote updates: add support for PBS remotes Lukas Wagner
2025-10-17 12:10 ` [pdm-devel] [PATCH datacenter-manager v2 10/13] api: add APT endpoints " Lukas Wagner
2025-10-17 12:10 ` [pdm-devel] [PATCH datacenter-manager v2 11/13] ui: add remote update view Lukas Wagner
2025-10-21 19:18   ` Thomas Lamprecht
2025-10-22 10:22     ` Lukas Wagner
2025-10-23  8:36       ` Thomas Lamprecht
2025-10-23 13:01         ` Lukas Wagner [this message]
2025-10-17 12:10 ` [pdm-devel] [PATCH datacenter-manager v2 12/13] ui: show new remote update view in the 'Remotes' section Lukas Wagner
2025-10-17 12:10 ` [pdm-devel] [PATCH datacenter-manager v2 13/13] remote updates: avoid unnecessary clone Lukas Wagner
2025-10-23 12:47 ` [pdm-devel] superseded: [PATCH datacenter-manager v2 00/13] add global remote update view Lukas Wagner

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=DDPPZDYQO4HV.2R50SHMKANKEZ@proxmox.com \
    --to=l.wagner@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal