[pve-devel] [PATCH manager 1/2] close #4369: api: optionally only suggest unique IDs

[DERUMIER, Alexandre]

>>The pmxcfs filesystem has limits, and I do not really want to waste
>>space for such things. I would prefer the run-length encoded list.

>>@Alexandre: Why do you want to keep a backup of old config files?

Don't need content of old config. ( I have backup anyway).

I was more thinking about something "atomic" delete, like a simple
vmid.conf move could be done, where we can do a lot of delete in //
without need to lock a global variable.

To be honest, I don't known enough the internal of pxmcfs to known what
is the best method.

My main problems currently is limitation of // for vm create/delete
when we create vms with automation scripts.




Talking about unique ID, any plan (longterm) to implement (optionnal)
uuid one day ? (I known that it's a lot of work, but it could be
usefull to be able to share storage between differents cluster, and be
able to move vms between them without need to rewrite volume datas with
different id)



-------- Message initial --------
De: Dietmar Maurer <dietmar at proxmox.com>
À: Severen Redwood <severen.redwood at sitehost.co.nz>, Proxmox VE
development discussion <pve-devel at lists.proxmox.com>, Alexandre
Derumier <alexandre.derumier at groupe-cyllene.com>
Objet: Re: [pve-devel] [PATCH manager 1/2] close #4369: api: optionally
only suggest unique IDs
Date: 30/09/2024 09:50:25

> This approach would also use more storage as you now have the
> overhead
> of FS metadata for every single ID you have marked as used.
> 
> Dietmar, what do you think is the best option here? I'm personally
> leaning towards using the list with your run-length encoding
> suggestion,
> but I'm open to implementing Alexandre's idea if you think it's worth
> it.

The pmxcfs filesystem has limits, and I do not really want to waste
space for such things. I would prefer the run-length encoded list.

@Alexandre: Why do you want to keep a backup of old config files?