From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id 90E751FF165 for ; Wed, 29 Jan 2025 11:52:16 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 514341FCEC; Wed, 29 Jan 2025 11:52:15 +0100 (CET) From: Dominik Csapak To: pdm-devel@lists.proxmox.com Date: Wed, 29 Jan 2025 11:51:39 +0100 Message-Id: <20250129105142.1291843-1-d.csapak@proxmox.com> X-Mailer: git-send-email 2.39.5 MIME-Version: 1.0 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.021 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [lib.rs, mod.rs, tree.rs] Subject: [pdm-devel] [RFC PATCH datacenter-manager 0/3] implement bulk start X-BeenThere: pdm-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox Datacenter Manager development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox Datacenter Manager development discussion Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pdm-devel-bounces@lists.proxmox.com Sender: "pdm-devel" Sending as RFC, because it's still very rough and i want to get some early feedback. This series implements an api call 'bulk-start' which is running on the pdm itself, that mimics the bulkstart from pve, but without the node limitation of pve. Does that make sense? Or would it be better to try to implement that on pve side? The advantage we have here is that we have an external view of the cluster, which means that things like node failures, synchronisation, etc. are much easier to handle. If we'd implment something like this on PVE, there has to be a node that has control of the api calls to make (or to schedule something via pmxcfs) and that is probably much harder to do there (pmxcfs sync queue) or brings some problems with it (node dies in the middle of an api call) It's very early, so please don't judge the actual api call code just now, I'd extend it with failure resulotion, polling the task, etc. OTOH there is the question if the UI makes sense this way, or if we want to combine the 'select to view details' and 'select to to a bulk action' into one. Or if we want to do the bulk actions more like in pve with a popup that shows the vm list again. Dominik Csapak (3): server: pve api: add new bulkstart api call pdm-client: add bulk_start method ui: pve tree: add bulk start action lib/pdm-client/src/lib.rs | 9 ++- server/src/api/pve/mod.rs | 98 +++++++++++++++++++++++++++- ui/src/pve/tree.rs | 133 ++++++++++++++++++++++++++++++++++++-- 3 files changed, 234 insertions(+), 6 deletions(-) -- 2.39.5 _______________________________________________ pdm-devel mailing list pdm-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pdm-devel