[pve-devel] [RFC guest-common 09/13] vzdump: schema: add fleecing property string

Fiona Ebner f.ebner at proxmox.com
Thu Feb 1 14:27:07 CET 2024

Am 01.02.24 um 14:20 schrieb DERUMIER, Alexandre:
> -------- Message initial --------
> De: Fiona Ebner <f.ebner at proxmox.com>
> À: Proxmox VE development discussion <pve-devel at lists.proxmox.com>,
> "DERUMIER, Alexandre" <alexandre.derumier at 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.

More information about the pve-devel mailing list