Re: [pdm-devel] [RFC PATCH datacenter-manager 0/2] use streaming content api

[Dominik Csapak <d.csapak@proxmox.com>]

one thing i forgot to ask here is:

how should we handle pbs3/4 compatibility?
We have IMHO the following options:

* Implement a fallback in the UI for pbs3
    can be ok, we could duplicate the panel and drop
    the old one when pbs3 is not supported anymore?
* Implement a fallback in the API for pbs3
    most robust solution IMO, gui can stay mostly the same, code
    should not be that much, can also be dropped if we don't
    want to support pbs3 anymore
* don't support pbs3 at all
    not really an option i think
* also commit the changes to pbs stable-3 branch
    maybe the easiest way, but here's the question
    where we draw the line for older products
    regarding features/bugs/etc.



On 10/8/25 3:56 PM, Dominik Csapak wrote:
> instead of using the snapshot list + a namespace selector, use the
> content api call [0] to show the whole tree.
> 
> Sending as RFC because there are some crucial parts missing in the ui
> (see the commit message of 2/2) but I wanted to get early feedback and
> send out some patches so one can test the streaming content api call
> in the pdm ui.
> 
> 0: https://lore.proxmox.com/pbs-devel/20251008134344.3512958-1-d.csapak@proxmox.com/
> 
> Dominik Csapak (2):
>    server: add new streaming 'content' api call for pbs
>    ui: pbs: snapshot list: change to streaming 'content' api call
> 
>   server/src/api/pbs/mod.rs   |  40 +++++++++-
>   server/src/pbs_client.rs    |  51 +++++++++++++
>   ui/src/pbs/snapshot_list.rs | 148 +++++++++++++++++++++++++-----------
>   3 files changed, 193 insertions(+), 46 deletions(-)
> 



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