Re: [PVE-User] VMID clarifying
and then others will argue that they don't want that space polluted by random numbers... (i'm personnaly encoding IPs in the PVID and let the lower numbers for testing) it's simple, if your using the GUI, just enter a random number (maybe c from a rnd generator). if your using an api call, just let your caller generate a random number. Tom Am Dienstag, den 22.10.2019, 16:47 +0200 schrieb lists: > ok, have read it. > > Pity, the outcome. > > Reading that the final suggestion is: using a random number, then > perhaps pve could simply suggest a random PVID number between 1 and > 4 > billion. > > (and if already in use: choose another random number) > > No need to store anything anywhere, and chances of duplicating a > PVID > would be virtually zero. > > MJ > > On 22-10-2019 16:19, Dominik Csapak wrote: > > there was already a lengthy discussion of this topic on the > > bugtracker > > see https://bugzilla.proxmox.com/show_bug.cgi?id=1822 > > > > ___ > > pve-user mailing list > > pve-user@pve.proxmox.com > > https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user > > ___ > pve-user mailing list > pve-user@pve.proxmox.com > https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user ___ pve-user mailing list pve-user@pve.proxmox.com https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
Re: [PVE-User] VMID clarifying
ok, have read it. Pity, the outcome. Reading that the final suggestion is: using a random number, then perhaps pve could simply suggest a random PVID number between 1 and 4 billion. (and if already in use: choose another random number) No need to store anything anywhere, and chances of duplicating a PVID would be virtually zero. MJ On 22-10-2019 16:19, Dominik Csapak wrote: there was already a lengthy discussion of this topic on the bugtracker see https://bugzilla.proxmox.com/show_bug.cgi?id=1822 ___ pve-user mailing list pve-user@pve.proxmox.com https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user ___ pve-user mailing list pve-user@pve.proxmox.com https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
Re: [PVE-User] VMID clarifying
there was already a lengthy discussion of this topic on the bugtracker see https://bugzilla.proxmox.com/show_bug.cgi?id=1822 ___ pve-user mailing list pve-user@pve.proxmox.com https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
Re: [PVE-User] VMID clarifying
or better, start with VMID 1, then +n --- Gilberto Nunes Ferreira (47) 3025-5907 (47) 99676-7530 - Whatsapp / Telegram Skype: gilberto.nunes36 Em ter, 22 de out de 2019 às 11:05, lists escreveu: > Hi, > > Actually, we feel the same as Gilberto. > > Could proxmox not for example default to something like: highest > currently-in-use-number PLUS 1? > > MJ > > On 22-10-2019 15:28, Fabian Grünbichler wrote: > > On October 22, 2019 2:43 pm, Gilberto Nunes wrote: > >> Folks, > >> When you create a VM, it generates an ID, for example 100, 101, 102 ... > etc > > > > no. when you create a VM in the GUI, it suggests the first free slot in > > the guest ID range. you can choose whatever you want ;) > > > >> ... > >> By removing this VM 101 let's say, and then creating a new one, I > noticed > >> that it generates this new one with ID 101 again. > > > > only if you don't set another ID. > > > >> But I also realized that it takes the backups I had from the old VM 101 > and > >> links to this new one, even though it's OSs and everything else. My > fear is > >> that running a backup routine will overwrite the images I had with that > ID. > >> It would probably happen if I had not realized. > > > > the solution is to either not delete VMs that are still important (even > > if 'important' just means having the associated backups semi-protected) > > > >> Any way to use sequential ID and not go back in IDs? I do not know if i > was > >> clear > > > > or don't use the default VMID suggestion by the GUI. there is no way to > > change that behaviour, since we don't have a record of "IDs that (might) > > have been used at some point in the past" > > > > ___ > > pve-user mailing list > > pve-user@pve.proxmox.com > > https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user > > > ___ > pve-user mailing list > pve-user@pve.proxmox.com > https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user > ___ pve-user mailing list pve-user@pve.proxmox.com https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
Re: [PVE-User] VMID clarifying
Hi, Actually, we feel the same as Gilberto. Could proxmox not for example default to something like: highest currently-in-use-number PLUS 1? MJ On 22-10-2019 15:28, Fabian Grünbichler wrote: On October 22, 2019 2:43 pm, Gilberto Nunes wrote: Folks, When you create a VM, it generates an ID, for example 100, 101, 102 ... etc no. when you create a VM in the GUI, it suggests the first free slot in the guest ID range. you can choose whatever you want ;) ... By removing this VM 101 let's say, and then creating a new one, I noticed that it generates this new one with ID 101 again. only if you don't set another ID. But I also realized that it takes the backups I had from the old VM 101 and links to this new one, even though it's OSs and everything else. My fear is that running a backup routine will overwrite the images I had with that ID. It would probably happen if I had not realized. the solution is to either not delete VMs that are still important (even if 'important' just means having the associated backups semi-protected) Any way to use sequential ID and not go back in IDs? I do not know if i was clear or don't use the default VMID suggestion by the GUI. there is no way to change that behaviour, since we don't have a record of "IDs that (might) have been used at some point in the past" ___ pve-user mailing list pve-user@pve.proxmox.com https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user ___ pve-user mailing list pve-user@pve.proxmox.com https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
Re: [PVE-User] Strange behavior vzdump
Mandi! Gilberto Nunes In chel di` si favelave... > I have notice that vzdump options, maxfiles doesn't work properly. > I set --maxfiles to 10, but still it's hold old files... > For now, I add --remove 1, to the /etc/vzdump.conf, but, according to the > vzdump man page, default --remove set is 1, i.e., enable! > Why vzdump do not remove old backup, just when set maxfiles?? > Or even worst, if --remove 1 is the default options, why vzdump doesn't > work?? > Proxmox VE version 5.4 This make some noise on my ear... two clusters, one with ''traditional'' iSCSI SAN storage, one with Ceph. On Ceph one: root@hulk:~# ls /srv/pve/dump/ | grep \.lzo | cut -d '-' -f 1-3 | sort | uniq -c 1 vzdump-lxc-103 1 vzdump-lxc-105 1 vzdump-lxc-106 1 vzdump-lxc-109 3 vzdump-lxc-111 50 vzdump-lxc-114 49 vzdump-lxc-117 1 vzdump-qemu-104 3 vzdump-qemu-108 3 vzdump-qemu-113 1 vzdump-qemu-115 49 vzdump-qemu-116 My backup stategy is: + for some VM/LXC, daily backup (114, 116, 117 are 'daily') all day's week apart saturday. + for all VM/LXC, on saturday bacula pre-script that run the backup, and then bacula put on tape. the bacula 'pre' script do: /usr/bin/vzdump 117 -storage Backup -maxfiles 1 -remove -compress lzo -mode suspend -quiet -mailto c...@sv.lnf.it -mailnotification failure for every LXC/VM, and as you can see, delete old backup only for some VM/LXC, not all. 'backup' storage is defined as: nfs: Backup export /srv/pve path /mnt/pve/Backup server 10.27.251.11 content vztmpl,images,iso,backup,rootdir maxfiles 0 options vers=3,soft,intr Clearly, no error in logs. -- dott. Marco Gaiarin GNUPG Key ID: 240A3D66 Associazione ``La Nostra Famiglia'' http://www.lanostrafamiglia.it/ Polo FVG - Via della Bontà, 7 - 33078 - San Vito al Tagliamento (PN) marco.gaiarin(at)lanostrafamiglia.it t +39-0434-842711 f +39-0434-842797 Dona il 5 PER MILLE a LA NOSTRA FAMIGLIA! http://www.lanostrafamiglia.it/index.php/it/sostienici/5x1000 (cf 00307430132, categoria ONLUS oppure RICERCA SANITARIA) ___ pve-user mailing list pve-user@pve.proxmox.com https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
Re: [PVE-User] VMID clarifying
On October 22, 2019 2:43 pm, Gilberto Nunes wrote: > Folks, > When you create a VM, it generates an ID, for example 100, 101, 102 ... etc no. when you create a VM in the GUI, it suggests the first free slot in the guest ID range. you can choose whatever you want ;) > ... > By removing this VM 101 let's say, and then creating a new one, I noticed > that it generates this new one with ID 101 again. only if you don't set another ID. > But I also realized that it takes the backups I had from the old VM 101 and > links to this new one, even though it's OSs and everything else. My fear is > that running a backup routine will overwrite the images I had with that ID. > It would probably happen if I had not realized. the solution is to either not delete VMs that are still important (even if 'important' just means having the associated backups semi-protected) > Any way to use sequential ID and not go back in IDs? I do not know if i was > clear or don't use the default VMID suggestion by the GUI. there is no way to change that behaviour, since we don't have a record of "IDs that (might) have been used at some point in the past" ___ pve-user mailing list pve-user@pve.proxmox.com https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
[PVE-User] Strange behavior vzdump
Hi there I have notice that vzdump options, maxfiles doesn't work properly. I set --maxfiles to 10, but still it's hold old files... For now, I add --remove 1, to the /etc/vzdump.conf, but, according to the vzdump man page, default --remove set is 1, i.e., enable! Why vzdump do not remove old backup, just when set maxfiles?? Or even worst, if --remove 1 is the default options, why vzdump doesn't work?? Proxmox VE version 5.4 Thanks --- Gilberto Nunes Ferreira (47) 3025-5907 (47) 99676-7530 - Whatsapp / Telegram Skype: gilberto.nunes36 ___ pve-user mailing list pve-user@pve.proxmox.com https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
[PVE-User] VMID clarifying
Folks, When you create a VM, it generates an ID, for example 100, 101, 102 ... etc ... By removing this VM 101 let's say, and then creating a new one, I noticed that it generates this new one with ID 101 again. But I also realized that it takes the backups I had from the old VM 101 and links to this new one, even though it's OSs and everything else. My fear is that running a backup routine will overwrite the images I had with that ID. It would probably happen if I had not realized. Any way to use sequential ID and not go back in IDs? I do not know if i was clear --- Gilberto Nunes Ferreira (47) 3025-5907 (47) 99676-7530 - Whatsapp / Telegram Skype: gilberto.nunes36 ___ pve-user mailing list pve-user@pve.proxmox.com https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
