From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Cc: pdm-devel@lists.proxmox.com
Subject: Re: [pdm-devel] [pve-devel] [RFC access-control/manager/proxmox{, -yew-comp, -datacenter-manager}/xtermjs 00/11] add remote node shell
Date: Thu, 06 Nov 2025 08:46:17 +0100 [thread overview]
Message-ID: <1762415138.7a3xhrktif.astroid@yuna.none> (raw)
In-Reply-To: <20251105141335.1230493-1-f.gruenbichler@proxmox.com>
and obviously this was actually intended for pdm-devel, even though 3/7
repos are PVE ones ;)
On November 5, 2025 3:13 pm, Fabian Grünbichler wrote:
> This RFC is a PoC for adding a node shell to PVE remotes. If the general
> direction is okay, it will be extended to cover PBS as well for a proper v1.
>
> The PVE remote side needs pve-access-control and pve-manager bumped, the PDM
> side needs pve-xtermjs and PDM itself bumped, proxmox and proxmox-yew-comp need
> bumps before building PDM with them included.
>
> pve-xtermjs:
>
> Fabian Grünbichler (1):
> xtermjs: add support for remote node shells via PDM
>
> xterm.js/src/main.js | 13 +++++++++++--
> 1 file changed, 11 insertions(+), 2 deletions(-)
>
>
> pve-access-control:
>
> Fabian Grünbichler (1):
> api: ticket: allow token-owned VNC ticket verification
>
> src/PVE/API2/AccessControl.pm | 40 +++++++++++++++++++++++------------
> 1 file changed, 27 insertions(+), 13 deletions(-)
>
>
> pve-manager:
>
> Fabian Grünbichler (2):
> api: termproxy/vncwebsocket: allow tokens
> api: termproxy: add description to return schema
>
> PVE/API2/Nodes.pm | 15 +++++++++------
> 1 file changed, 9 insertions(+), 6 deletions(-)
>
>
> proxmox:
>
> Fabian Grünbichler (2):
> pve-api-types: add termproxy call and types
> http: websocket: add proxy helper
>
> proxmox-http/src/websocket/mod.rs | 67 ++++++++++++++++++++++++
> pve-api-types/generate.pl | 2 +
> pve-api-types/pve-api.json | 4 ++
> pve-api-types/src/generated/code.rs | 20 +++++++-
> pve-api-types/src/generated/types.rs | 76 ++++++++++++++++++++++++++++
> 5 files changed, 168 insertions(+), 1 deletion(-)
>
>
> proxmox-yew-comp:
>
> Fabian Grünbichler (1):
> xtermjs: add remote support
>
> src/apt_package_manager.rs | 9 ++++++---
> src/xtermjs.rs | 38 +++++++++++++++++++++++++++++++++-----
> 2 files changed, 39 insertions(+), 8 deletions(-)
>
>
> proxmox-datacenter-manager:
>
> Fabian Grünbichler (4):
> connection: add access to "raw" client
> api: pve: add termproxy endpoint
> api: pve: add vncwebsocket endpoint
> ui: pve: node: add shell tab
>
> server/src/api/pve/node.rs | 259 +++++++++++++++++-
> server/src/connection.rs | 11 +
> .../src/metric_collection/collection_task.rs | 5 +
> server/src/test_support/fake_remote.rs | 5 +
> ui/src/pve/node/mod.rs | 19 +-
> 5 files changed, 293 insertions(+), 6 deletions(-)
>
>
> Summary over all repositories:
> 15 files changed, 547 insertions(+), 36 deletions(-)
>
> --
> Generated by git-murpp 0.8.1
>
>
> _______________________________________________
> pve-devel mailing list
> pve-devel@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
>
_______________________________________________
pdm-devel mailing list
pdm-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pdm-devel
parent reply other threads:[~2025-11-06 7:46 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20251105141335.1230493-1-f.gruenbichler@proxmox.com>]
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=1762415138.7a3xhrktif.astroid@yuna.none \
--to=f.gruenbichler@proxmox.com \
--cc=pdm-devel@lists.proxmox.com \
--cc=pve-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