[suggestion] Folders for VMS

[flourodbs]

Hi,

my suggestion is to have the possibility the create Folders, like on VMWare or even Active directory, to organize the VMS eg:

proxmox-1/
├─ development/
│ ├─ project-1/
│ │ ├─ vm1
│ │ ├─ vm2
├─ production/
│ ├─ project-1/
│ │ ├─ vm1


instead of the current one:

proxmox-1/
├─ vm1-project-1-production
├─ vm1-project-1-development

the folders would help too on backup, eg: with the folder tree above we only would like to backup production, so we select the folder production and it would only backup vms inside the folder instead of selection one by one and everytime we add a new add a new vm add on the backup list.


Edit: Might aswell add that instead of the tree starting on the servers, it should start on datacenter (like it is now) and inside the datacenter should be the servers and storages. Instead of vms going inside the servers it should start the created folders and inside the vm a field with information on which server are the resources allocated.

 

[LnxBil]

instead of the current one:

proxmox-1/
├─ vm1-project-1-production
├─ vm1-project-1-development

The current setup is more like:

datacenter/
|-- production
|   |-- project-1-vm-1
|   |-- project-1-vm-2
|-- development
|   |-- project-1-vm-1
|   |-- project-1-vm-2

or

datacenter/
|-- project-1-production
|   |-- vm-1
|   |-- vm-2
|-- project-1-development
|   |-- vm-1
|   |-- vm-2

with pools, but in general, I see your point and it is a good suggestion.

 

[flourodbs]

The current setup is more like:

datacenter/
|-- production
|   |-- project-1-vm-1
|   |-- project-1-vm-2
|-- development
|   |-- project-1-vm-1
|   |-- project-1-vm-2

or

datacenter/
|-- project-1-production
|   |-- vm-1
|   |-- vm-2
|-- project-1-development
|   |-- vm-1
|   |-- vm-2

with pools, but in general, I see your point and it is a good suggestion.

I don't use pools on my setup so mine is just the vms all together. What's the benefits for using pools? I don't see a good enough benefit to use them.

 

[LnxBil]

I don't use pools on my setup so mine is just the vms all together. What's the benefits for using pools? I don't see a good enough benefit to use them.

Is more organization not enough? Normally you can also set permissions based on pools, so that you project 1 members just see their project 1 pool.

 

[flourodbs]

Is more organization not enough? Normally you can also set permissions based on pools, so that you project 1 members just see their project 1 pool.

I mean it can work but imagine the following scenario: you are in a group of companies and every company has a project that requires 2 servers.

For that scenario I would rather have:
company-1 > Project-1 > vms
company-2 > project-1 > vms

instead of:
company-1-project-1 > vms
company-2-project-1 > vms

 

[gusmolva]

I mean it can work but imagine the following scenario: you are in a group of companies and every company has a project that requires 2 servers.

For that scenario I would rather have:
company-1 > Project-1 > vms
company-2 > project-1 > vms

instead of:
company-1-project-1 > vms
company-2-project-1 > vms

I am interested in this characteristic. I'm a teacher of computer science. I prepare different virtual machines for every topic. Then, If a student get lost, he can follow next topic using a clone of a virtual machine of that topic. If not, student begins to accumulate delays. Then, I need to organize my different states of virtual machines by subject and topics. It is similar as laboratories of Cisco or AWS when you follow a course. Thanks.