public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Daniel Krambrock via pve-devel <pve-devel@lists.proxmox.com>
To: pve-devel@lists.proxmox.com
Cc: Daniel Krambrock <krambrock@hrz.uni-marburg.de>
Subject: Re: [pve-devel] Continuing on making the VM ID suggestion strategy configurable
Date: Mon, 2 Sep 2024 12:44:44 +0200	[thread overview]
Message-ID: <mailman.510.1725274253.302.pve-devel@lists.proxmox.com> (raw)
In-Reply-To: <tzwlxcv5z7qacnzkaggl6sz67xsg7cpcktyqc4rulh5nnxm7vy@dviin2xi67un>

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

From: Daniel Krambrock <krambrock@hrz.uni-marburg.de>
To: pve-devel@lists.proxmox.com
Subject: Re: [pve-devel] Continuing on making the VM ID suggestion strategy configurable
Date: Mon, 2 Sep 2024 12:44:44 +0200
Message-ID: <30ea0b15-3fe1-43d2-a573-e7d41504371a@hrz.uni-marburg.de>

Hi everyone,

please excuse me for leaving this issue lying around. I am very pleased 
that Severen is interested in continuing this patch and takes over the work.

Am 30.08.24 um 01:08 schrieb Severen Redwood:
> 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.

You are of course right, only option 3 solves the problem as also 
Shannon pointed out.

> 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?

For me this is more then OK, thank you. In case it's still important: I 
have already signed the Harmony CLA.

Yours sincerely,
Daniel


[-- 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-09-02 10:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <tzwlxcv5z7qacnzkaggl6sz67xsg7cpcktyqc4rulh5nnxm7vy@dviin2xi67un>
2024-09-02 10:44 ` Daniel Krambrock via pve-devel [this message]
2024-08-29 23:08 Severen Redwood 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.510.1725274253.302.pve-devel@lists.proxmox.com \
    --to=pve-devel@lists.proxmox.com \
    --cc=krambrock@hrz.uni-marburg.de \
    /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