RFE: is vm virtual disk naming scheme optimal ?

RolandK

RolandK

Renowned Member
Proxmox Subscriber
Mar 5, 2019
999
214
88
52
i think that disk naming in it's current schmeme can be a little bit confusing.

it seems disk naming is done from pool/storage perspective and not from vm-perspective.

is this really perfect design or "well thought" if a vm has 3 (or even more) virtual disks which all have the same filename ? (but in different directories / storage pools ) ?

i have accidentally overwritten a virtual disk while copying/consolidating a virtual machine to another host outside our main cluster, that's why i'm asking myself why they are named like this.

i think this can easily lead to mistaking/confusion.


scsi0: vms-files-ssd:211/vm-211-disk-1.qcow2,aio=threads,discard=on,iothread=1,size=10G
scsi1: vm-files-hdd1:211/vm-211-disk-1.qcow2,aio=threads,discard=on,iothread=1,size=20G
scsi2: vms-files-hdd2:211/vm-211-disk-1.qcow2,aio=threads,discard=on,iothread=1,size=10G

/hddpool2/vms-files/images/211
/hddpool2/vms-files/images/211/vm-211-disk-1.qcow2
/hddpool/vms-files/images/211
/hddpool/vms-files/images/211/vm-211-disk-1.qcow2
/rpool/vms-files/images/211
/rpool/vms-files/images/211/vm-211-disk-1.qcow2
 
RolandK said:
i think that disk naming in it's current schmeme can be a little bit confusing.

it seems disk naming is done from pool/storage perspective and not from vm-perspective.

is this really perfect design or "well thought" if a vm has 3 (or even more) virtual disks which all have the same filename ? (but in different directories / storage pools ) ?

i have accidentally overwritten a virtual disk while copying/consolidating a virtual machine to another host outside our main cluster, that's why i'm asking myself why they are named like this.

i think this can easily lead to mistaking/confusion.


scsi0: vms-files-ssd:211/vm-211-disk-1.qcow2,aio=threads,discard=on,iothread=1,size=10G
scsi1: vm-files-hdd1:211/vm-211-disk-1.qcow2,aio=threads,discard=on,iothread=1,size=20G
scsi2: vms-files-hdd2:211/vm-211-disk-1.qcow2,aio=threads,discard=on,iothread=1,size=10G

/hddpool2/vms-files/images/211
/hddpool2/vms-files/images/211/vm-211-disk-1.qcow2
/hddpool/vms-files/images/211
/hddpool/vms-files/images/211/vm-211-disk-1.qcow2
/rpool/vms-files/images/211
/rpool/vms-files/images/211/vm-211-disk-1.qcow2
Click to expand...
The focus of disk naming scheme is rather the usage by system (scripts) than by humans. Assuming mainly WEB GUI is used for administration the name scheme is not very important for the user. However, it's possible to use the dedicated disk names and implemented as a feature to use them by CLI, this means also you can specify your own names too. There is maybe an improvement potential for the automatic naming scheme concept, I can imagine that e.g. customizing such a scheme is a solution. Feel free to open an "enhancement" entry in https://bugzilla.proxmox.com/ describing your request in detail. The more requests are made regarding a certain topic, the higher the chance of realization.
 
You must log in or register to reply here.
Top Bottom