From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <f.ebner@proxmox.com> Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id F242792266 for <pve-devel@lists.proxmox.com>; Thu, 1 Feb 2024 14:27:39 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id C978A105A5 for <pve-devel@lists.proxmox.com>; Thu, 1 Feb 2024 14:27:09 +0100 (CET) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [94.136.29.106]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS for <pve-devel@lists.proxmox.com>; Thu, 1 Feb 2024 14:27:08 +0100 (CET) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id 844A640B01; Thu, 1 Feb 2024 14:27:08 +0100 (CET) Message-ID: <c090848e-84d7-4513-a3f0-74c1f24f317a@proxmox.com> Date: Thu, 1 Feb 2024 14:27:07 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Content-Language: en-US To: "DERUMIER, Alexandre" <alexandre.derumier@groupe-cyllene.com>, "pve-devel@lists.proxmox.com" <pve-devel@lists.proxmox.com> References: <20240125144149.216064-1-f.ebner@proxmox.com> <20240125144149.216064-10-f.ebner@proxmox.com> <e541f8a0-4c11-4904-95cd-1e8d1c73bdc2@proxmox.com> <ee733a4ffeddddc5e2071c003bd5b58ea080c682.camel@groupe-cyllene.com> <1526d2b1-d71d-4bb7-b085-a7e3f059b9c3@proxmox.com> <82c2862f6906fd697b6862cbc6db433de219a2d9.camel@groupe-cyllene.com> From: Fiona Ebner <f.ebner@proxmox.com> In-Reply-To: <82c2862f6906fd697b6862cbc6db433de219a2d9.camel@groupe-cyllene.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL -0.073 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 SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record T_SCC_BODY_TEXT_LINE -0.01 - Subject: Re: [pve-devel] [RFC guest-common 09/13] vzdump: schema: add fleecing property string 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> X-List-Received-Date: Thu, 01 Feb 2024 13:27:40 -0000 Am 01.02.24 um 14:20 schrieb DERUMIER, Alexandre: > -------- Message initial -------- > De: Fiona Ebner <f.ebner@proxmox.com> > À: Proxmox VE development discussion <pve-devel@lists.proxmox.com>, > "DERUMIER, Alexandre" <alexandre.derumier@groupe-cyllene.com> > Objet: Re: [pve-devel] [RFC guest-common 09/13] vzdump: schema: add > fleecing property string > Date: 01/02/2024 14:11:20 > >>> But the question remains if the setting should be VM-specific or >>> job-wide. Most flexible would be both, but I'd rather not >>> overcomplicate >>> things. Maybe my idea for the default with "use same storage for >>> fleecing" is not actually a good one and having a dedicated storage >>> for >>> fleecing is better. Then it needs to be a conscious decision. > > Instead, couldn't we defined it in pbs storage ? > at vm level, we can't known which storage will be used. (one could be > fast without need of fleecing, another could be slow and need fleecing) > > storage.cfg: > > pbs : mypbs > fleecing-storage ..... > Backup fleecing is not limited to PBS and it's doesn't have anything to do with PBS implementation-wise, so this is not the right place for the setting IMHO. > An allow to override at job level ? A job-level option alone is already more flexible than defining it as part of the PBS-configuration.