public inbox for pdm-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Dominik Csapak <d.csapak@proxmox.com>
To: Proxmox Datacenter Manager development discussion
	<pdm-devel@lists.proxmox.com>,
	Lukas Wagner <l.wagner@proxmox.com>
Subject: [pdm-devel] applied:  [PATCH proxmox{-yew-comp, -datacenter-manager} v2 0/7] PVE node update view
Date: Thu, 4 Sep 2025 14:01:33 +0200	[thread overview]
Message-ID: <6e647ee8-76a7-4487-b2b4-8c20236112f3@proxmox.com> (raw)
In-Reply-To: <20250903114123.215787-1-l.wagner@proxmox.com>



On 9/3/25 1:41 PM, Lukas Wagner wrote:
> This series adds a new 'Updates' tab for PVE remotes. The existing status
> overview is moved to a new 'Overview' tab, which is visible by default.
> 
> On the backend side, we add a couple new API endpoints, which simply pass
> through the request to the PVE nodes, no caching for now.
> 
>    GET /pve/remotes/{remote}/nodes/{node}/apt
>       Get list of updatable packages
>    GET /pve/remotes/{remote}/nodes/{node}/changelog
>       Get list of changelog of package
>    POST /pve/remotes/{remote}/nodes/{node}/apt
>       Update APT package database
> 
> In terms of permissions, these new API endpoints require RESOURCE_MODIFY privs on
>      /resource/{remote}/node/{node}/system
> 
> This was the result of a short discussion in the development chat room.
> 
> The existing APT view component is a bit large for this panel, maybe we could
> hide the package description by default (but not too important for now).
> 
> Future work (some backend work already started, but can't finish before my
> vacation):
> 
>    - "Global Update" view that lists update status of all remote nodes
>    - Cache update status per node (absolutely necessary for the 'global' view),
>      with a task refreshing the update status every couple of hours
>    - Maybe send a notification about the global update availabilty (require notification
>      stack integration first)
>    - Add new API functions to pdm-client crate and CLI
>    - Allow package upgrade (requires web socket proxying, as far as I can see,
>      haven't really looked into it much)
> 
> Changes since v1:
>    - consistently return errors for PBS remotes
>    - drop already applied patches
> 
> Some of the notes from Stefan's review notes were not addressed, see my replies
> for v1 for details.
> 
> 
> proxmox-yew-comp:
> 
> Lukas Wagner (2):
>    apt view: allow to set task_base_url
>    apt view: reload if base urls have changed
> 
>   src/apt_package_manager.rs | 23 +++++++++++++++++++++++
>   1 file changed, 23 insertions(+)
> 
> 
> proxmox-datacenter-manager:
> 
> Lukas Wagner (5):
>    update proxmox-api-types submodule
>    server: add api for getting available updates/changelogs for remote
>      nodes
>    ui: pve: promote node.rs to dir-style module
>    ui: pve: move node overview to a new overview tab
>    ui: pve: node: add update tab
> 
>   lib/proxmox-api-types                    |   2 +-
>   server/src/api/pve/apt.rs                | 119 +++++++++++++++++++++++
>   server/src/api/pve/mod.rs                |   3 +-
>   server/src/api/pve/node.rs               |   1 +
>   server/src/lib.rs                        |   1 +
>   server/src/remote_updates.rs             |  89 +++++++++++++++++
>   ui/src/pve/node/mod.rs                   | 103 ++++++++++++++++++++
>   ui/src/pve/{node.rs => node/overview.rs} |  31 +++---
>   8 files changed, 327 insertions(+), 22 deletions(-)
>   create mode 100644 server/src/api/pve/apt.rs
>   create mode 100644 server/src/remote_updates.rs
>   create mode 100644 ui/src/pve/node/mod.rs
>   rename ui/src/pve/{node.rs => node/overview.rs} (95%)
> 
> 
> Summary over all repositories:
>    9 files changed, 350 insertions(+), 22 deletions(-)
> 


applied, thanks!
i pushed some follow ups like discussed. we still need to bump yew-comp 
and update the dependency


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


      parent reply	other threads:[~2025-09-04 12:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-03 11:41 [pdm-devel] " Lukas Wagner
2025-09-03 11:41 ` [pdm-devel] [PATCH proxmox-yew-comp v2 1/2] apt view: allow to set task_base_url Lukas Wagner
2025-09-03 11:41 ` [pdm-devel] [PATCH proxmox-yew-comp v2 2/2] apt view: reload if base urls have changed Lukas Wagner
2025-09-03 11:41 ` [pdm-devel] [PATCH proxmox-datacenter-manager v2 1/5] update proxmox-api-types submodule Lukas Wagner
2025-09-03 11:41 ` [pdm-devel] [PATCH proxmox-datacenter-manager v2 2/5] server: add api for getting available updates/changelogs for remote nodes Lukas Wagner
2025-09-03 11:41 ` [pdm-devel] [PATCH proxmox-datacenter-manager v2 3/5] ui: pve: promote node.rs to dir-style module Lukas Wagner
2025-09-03 11:41 ` [pdm-devel] [PATCH proxmox-datacenter-manager v2 4/5] ui: pve: move node overview to a new overview tab Lukas Wagner
2025-09-03 11:41 ` [pdm-devel] [PATCH proxmox-datacenter-manager v2 5/5] ui: pve: node: add update tab Lukas Wagner
2025-09-04  9:30 ` [pdm-devel] [PATCH proxmox{-yew-comp, -datacenter-manager} v2 0/7] PVE node update view Dominik Csapak
2025-09-04  9:57   ` Thomas Lamprecht
2025-09-04 12:01 ` Dominik Csapak [this message]

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=6e647ee8-76a7-4487-b2b4-8c20236112f3@proxmox.com \
    --to=d.csapak@proxmox.com \
    --cc=l.wagner@proxmox.com \
    --cc=pdm-devel@lists.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