Hi all,
Firstly, let me say great work on the 2.x upgrade, looks and feels much better and with the added functionality too...
We are currently heavily testing VE2.1 in readiness for deployment into our corporate environment (currently 1.9) and we seem to have hit a snag involving pools. I have added several groups, users and pools, set permissions (lots of hit and miss but it's all part of the fun) and added LDAP auth all with relative ease and no big issues. A problem we are seeing right now is when a user belonging to a pool tries to create a VM, Proxmox issues the VMID which is next in order from the highest numbered VM within the Pool - Problem.
This is what has happened:
1. 5 Pools (two being used for testing, why complicate things, right?) created with permissions set per group with users added to the appropriate group
2. The pools being used for testing have some VMs in - 101, 102 pool 1 and 103, 104 pool 2
3. If I log in as a user who only has permissions in Pool 1 and create a VM, the VMID automatically generated is 103 and here lies the issue. It's nice that Proxmox won't actually create the VM but is there a way around this?
4. If I log in as an Admin user, I can create a VM and the VMID numbering sequence runs in order.
This test system was build from 1.9 and upgraded using the script. All VMs were backed up and removed from the original cluster and restored as set out in the how to guide (Brilliant work btw). Currently the test system is using local storage but our Live system is running a SAN with a large, flat LV.
Firstly, let me say great work on the 2.x upgrade, looks and feels much better and with the added functionality too...
We are currently heavily testing VE2.1 in readiness for deployment into our corporate environment (currently 1.9) and we seem to have hit a snag involving pools. I have added several groups, users and pools, set permissions (lots of hit and miss but it's all part of the fun) and added LDAP auth all with relative ease and no big issues. A problem we are seeing right now is when a user belonging to a pool tries to create a VM, Proxmox issues the VMID which is next in order from the highest numbered VM within the Pool - Problem.
This is what has happened:
1. 5 Pools (two being used for testing, why complicate things, right?) created with permissions set per group with users added to the appropriate group
2. The pools being used for testing have some VMs in - 101, 102 pool 1 and 103, 104 pool 2
3. If I log in as a user who only has permissions in Pool 1 and create a VM, the VMID automatically generated is 103 and here lies the issue. It's nice that Proxmox won't actually create the VM but is there a way around this?
4. If I log in as an Admin user, I can create a VM and the VMID numbering sequence runs in order.
This test system was build from 1.9 and upgraded using the script. All VMs were backed up and removed from the original cluster and restored as set out in the how to guide (Brilliant work btw). Currently the test system is using local storage but our Live system is running a SAN with a large, flat LV.
