[pdm-devel] [PATCH datacenter-manager v2 11/13] ui: add remote update view

[Lukas Wagner]

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!