[pve-devel] [PATCH cluster v2 6/6] datacenter config: add unique-next-id to schema

--- Begin Message --- Add the `unique-next-id` property to the datacentre config schema to track whether only unique (ie. neither currently nor previously in use) VM/CT IDs should be suggested by the `/cluster/nextid` API endpoint. Co-authored-by: Daniel Krambrock Signed-off-by: Severen Redwood

[pve-devel] [PATCH cluster v2 5/6] cluster files: add used_vmids.list

--- Begin Message --- Add `/etc/pve/used_vmids.list` to the list of cluster files, which will be used for recording previously used VM/CT IDs. This is required so that we can optionally ensure that such IDs are not suggested by the `/cluster/nextid` API endpoint. Co-authored-by: Daniel Krambrock

[pve-devel] [PATCH qemu-server v2] api: record VM ID as used after a virtual machine is destroyed

--- Begin Message --- After a virtual machine is destroyed, record that its ID has been used via the `PVE::UsedVmidList` module so that the `/cluster/nextids` endpoint can later optionally avoid suggesting previously used IDs. Co-authored-by: Daniel Krambrock Signed-off-by: Severen Redwood ---

[pve-devel] [PATCH container v2] api: record CT ID as used after a container is destroyed

--- Begin Message --- After a container is destroyed, record that its ID has been used via the `PVE::UsedVmidList` module so that the `/cluster/nextids` endpoint can later optionally avoid suggesting previously used IDs. Co-authored-by: Daniel Krambrock Signed-off-by: Severen Redwood --- src/PV

[pve-devel] [PATCH manager v2 2/2] close #4369: ui: add datacenter option for unique VM/CT IDs

--- Begin Message --- Add a 'suggest unique VMIDs' row to the datacenter options page that allows choosing whether the `/cluster/nextid` API endpoint (and thereby any UI elements that suggest IDs) should avoid suggesting previously used IDs. This option defaults to off to ensure that this change in

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

--- Begin Message --- At the moment, the `/cluster/nextid` API endpoint will return the lowest available VM/CT ID, which means that it will suggest re-using VM IDs. This can be undesirable, so add an optional check to ensure that it chooses an ID which is not and has never been in use. This option

[pve-devel] [PATCH SERIES v2] Add ability to prevent suggesting previously used VM/CT IDs

--- Begin Message --- Hi everyone, This patch series is an updated version of my previous series [1] adding optional support for preventing PVE from suggesting previously used VM/CT IDs. The ID list is now read into a hash rather than an array so that O(1) membership tests can be used when `/clus

Re: [pve-devel] [PATCH pve-manager 2/3] Fix #5708: Add CPU raw counters

On 9/30/24 08:17, Sascha Westermann wrote: If the data is also to be processed by external metric servers, I think the integration in `PVE::ProcFSTools::read_proc_stat()` makes sense. The term `cpustat` would no longer conflict in this case, as the content would be virtually the same. I would cre

[pve-devel] Improvement suggestion for "Overrule active shutdown tasks" options

--- Begin Message --- Hi, I noticed in the latest proxmox 8.2.x that an "Overrule active shutdown tasks" option appeared when I want to force stop a VM - GREAT!!! I think the implementation is a bit limited and here are some proposed enhancements: - It should be possible to override not only shut

[pve-devel] [PATCH docs] increase verbosity of sdn dhcp docs.

These minor additions to and rearrangements within the documentation target easier accessibility for the SDN DHCP feature. Signed-off-by: Daniel Herzig --- pvesdn.adoc | 37 + 1 file changed, 29 insertions(+), 8 deletions(-) diff --git a/pvesdn.adoc b/pvesdn.