public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Severen Redwood via pve-devel <pve-devel@lists.proxmox.com>
To: pve-devel@lists.proxmox.com
Cc: Severen Redwood <severen.redwood@sitehost.co.nz>
Subject: [pve-devel] Continuing on making the VM ID suggestion strategy configurable
Date: Fri, 30 Aug 2024 11:08:07 +1200	[thread overview]
Message-ID: <mailman.472.1724973432.302.pve-devel@lists.proxmox.com> (raw)

[-- Attachment #1: Type: message/rfc822, Size: 4862 bytes --]

From: Severen Redwood <severen.redwood@sitehost.co.nz>
To: pve-devel@lists.proxmox.com
Subject: Continuing on making the VM ID suggestion strategy configurable
Date: Fri, 30 Aug 2024 11:08:07 +1200
Message-ID: <tzwlxcv5z7qacnzkaggl6sz67xsg7cpcktyqc4rulh5nnxm7vy@dviin2xi67un>

Hi everyone,

Something I've been running into with PVE is that VM IDs may be re-used
and that the UI will in fact suggest the smallest available ID (via the
`/cluster/nextid` endpoint), regardless of whether that ID has
previously been used or not. This can cause issues with PBS as it keys
backups by VM ID, which is detailed on this Bugzilla issue [1], so for
brevity I won't replicate the discussion here.

There's a patch series [2] from a few months ago which addresses this by
making the VM ID suggestion strategy configurable with the following
options:

1. Use the smallest ID that is not currently in use (current behaviour).
2. Use one greater than the largest ID in use.
3. Use the smallest ID that is neither currently nor previously in use.

In particular, option 3 is the one that would best solve the problem for
me.

However, the patches are stuck on some unresolved feedback and the
author (CC'd in) seems to have either paused or abandoned work on the
feature. For this reason, I'm interested in picking up where they left
off to get the feature to an acceptable state. Is this OK? And how
feasible is it that this feature would ultimately be accepted? At the
moment, the only nontrivial issue raised with the patches seems to be
regarding where the list of previously used VM IDs should be stored,
which I believe should be resolvable.

Thanks,
Severen

[1]: https://bugzilla.proxmox.com/show_bug.cgi?id=4369#c13
[2]: https://lore.proxmox.com/pve-devel/D1RYIAHXBOIH.RM5K01KGND9T@proxmox.com/t/

P.S. This is my first time using a mailing list, so please let me know
about any inadvertent breaches of etiquette :)


[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

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

             reply	other threads:[~2024-08-29 23:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-29 23:08 Severen Redwood via pve-devel [this message]
     [not found] <tzwlxcv5z7qacnzkaggl6sz67xsg7cpcktyqc4rulh5nnxm7vy@dviin2xi67un>
2024-09-02 10:44 ` Daniel Krambrock via pve-devel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=mailman.472.1724973432.302.pve-devel@lists.proxmox.com \
    --to=pve-devel@lists.proxmox.com \
    --cc=severen.redwood@sitehost.co.nz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal