Re: [pve-devel] [RFC PATCH manager] WIP: api: implement node-independent bulk actions

2025-03-20 Thread Stefan Hanreich
On 3/19/25 10:04, Dominik Csapak wrote: > On 3/18/25 12:30, Stefan Hanreich wrote: >>> There are alternative methods to achieve similar results: >>> * use some kind of queuing system on the cluster (e.g. via pmxcfs) >>> * using the 'startall'/'stopall' calls from pve in PDM >>> * surely some other

Re: [pve-devel] [RFC PATCH manager] WIP: api: implement node-independent bulk actions

2025-03-19 Thread Dominik Csapak
On 3/18/25 12:30, Stefan Hanreich wrote: This would be really interesting for applying the SDN configuration as well, where I'm currently calling the existing bulk-call. Really like the design with the start / check callbacks, that should make this quite flexible. On 3/18/25 11:39, Dominik Csapa

Re: [pve-devel] [RFC PATCH manager] WIP: api: implement node-independent bulk actions

2025-03-18 Thread Stefan Hanreich
This would be really interesting for applying the SDN configuration as well, where I'm currently calling the existing bulk-call. Really like the design with the start / check callbacks, that should make this quite flexible. On 3/18/25 11:39, Dominik Csapak wrote: > To achieve this, we start a work

[pve-devel] [RFC PATCH manager] WIP: api: implement node-independent bulk actions

2025-03-18 Thread Dominik Csapak
To achieve this, we start a worker task and use our generic api client to start the tasks on the relevant nodes. The client always points to 'localhost' so we let the pveproxy worry about the proxying etc. We reuse some logic from the startall/stopall/etc. calls, like getting the ordered guest inf