From eee1c5de0a337297fb05b34fdf40e444faaffca7 Mon Sep 17 00:00:00 2001 From: Thomas Lamprecht Date: Fri, 29 Apr 2022 17:29:12 +0200 Subject: [PATCH] pvecm: add basic next-id section Signed-off-by: Thomas Lamprecht --- pvecm.adoc | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) diff --git a/pvecm.adoc b/pvecm.adoc index 2af6828..ab1fbe7 100644 --- a/pvecm.adoc +++ b/pvecm.adoc @@ -1259,6 +1259,26 @@ it is likely that some nodes will boot faster than others. Please keep in mind that guest startup is delayed until you reach quorum. +[[pvecm_next_id_range]] +Guest VMID Auto-Selection +------------------------ + +When creating new guests the web interface will ask the backend for a free VMID +automatically. The default range for searching is `100` to `1000000` (lower +than the maximal allowed VMID enforced by the schema). + +Sometimes admins either want to allocate new VMIDs in a separate range, for +example to easily separate temporary VMs with ones that choose a VMID manually. +Other times its just desired to provided a stable length VMID, for which +setting the lower boundary to, for example, `100000` gives much more room for. + +To accommodate this use case one can set either lower, upper or both boundaries +via the `datacenter.cfg` configuration file, which can be edited in the web +interface under 'Datacenter' -> 'Options'. + +NOTE: The range is only used for the next-id API call, so it isn't a hard +limit. + Guest Migration --------------- -- 2.39.2