From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <pve-devel-bounces@lists.proxmox.com>
Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68])
	by lore.proxmox.com (Postfix) with ESMTPS id AAE2C1FF164
	for <inbox@lore.proxmox.com>; Fri,  3 Jan 2025 13:37:31 +0100 (CET)
Received: from firstgate.proxmox.com (localhost [127.0.0.1])
	by firstgate.proxmox.com (Proxmox) with ESMTP id 9CDDE1D365;
	Fri,  3 Jan 2025 13:37:22 +0100 (CET)
Message-ID: <b14258bb-fe39-4328-8645-4b6077b0a765@proxmox.com>
Date: Fri, 3 Jan 2025 13:37:19 +0100
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: Thomas Lamprecht <t.lamprecht@proxmox.com>,
 Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
 Max Carrara <m.carrara@proxmox.com>
References: <20241220185207.519912-1-m.carrara@proxmox.com>
 <9e522634-51ff-493a-bcdb-aba560d17d6a@proxmox.com>
 <47ba1e8e-c5d1-4873-91c4-9927b3b72e8c@proxmox.com>
 <D6RPJ276WHKU.1WEFTKRBGG5PN@proxmox.com>
 <c7698f04-5e13-413c-90bc-1332327bd779@proxmox.com>
 <66a4dca4-d3d7-4def-8f25-e23a2fcaefe5@proxmox.com>
Content-Language: en-US
From: Fiona Ebner <f.ebner@proxmox.com>
In-Reply-To: <66a4dca4-d3d7-4def-8f25-e23a2fcaefe5@proxmox.com>
X-SPAM-LEVEL: Spam detection results:  0
 AWL -0.051 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
Subject: Re: [pve-devel] [PATCH v2 pve-common 00/12] Introduce and Package
 PVE::Path & PVE::Filesystem
X-BeenThere: pve-devel@lists.proxmox.com
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Proxmox VE development discussion <pve-devel.lists.proxmox.com>
List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-devel>, 
 <mailto:pve-devel-request@lists.proxmox.com?subject=unsubscribe>
List-Archive: <http://lists.proxmox.com/pipermail/pve-devel/>
List-Post: <mailto:pve-devel@lists.proxmox.com>
List-Help: <mailto:pve-devel-request@lists.proxmox.com?subject=help>
List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel>, 
 <mailto:pve-devel-request@lists.proxmox.com?subject=subscribe>
Reply-To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: pve-devel-bounces@lists.proxmox.com
Sender: "pve-devel" <pve-devel-bounces@lists.proxmox.com>

Thank you for the detailed answer and sketching out the plans for the
transition to Rust and when perlmod should be used. That clarifies a lot
for me!

Just wanted to ask about more details for the qemu-server example. Let's
say we get to a point where it is nicely split up into dedicated modules
and we can use storage functionality from Rust already. How would we go
about translating qemu-server to Rust then? Start by translating the
lower-level modules (e.g. QMP, memory, CPU, ...) using perlmod to
preserve the functionality for existing callers and then in a second
step, switch over the API endpoints one-by-one? Or do you have a
different way in mind?


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