We have multiple teams, each working with their own resource pools. Each user/team only has permissions to create VM's in their own pool(s) using the VM.Allocate permission on their own pool(s). When creating new VM's that works well.
However when restoring a backup (From the Datastore -> Backups screen) it seems that we are unable to specify which pool to restore into. As users are not allowed to create VM's outside of their own pool(s) that results in an access-denied error. Allowing the VM.Allocate permission on the root, rather than specific pools, allows importing the VM's normally. However that's obviously not what we would want to do.
Are there better ways to restrict users to pools that still allows them to import backups? Or would this simply be a usecase that hasn't been implemented, requiring a pool-selection dropdown to be added to the Restore screen?
Thanks!
However when restoring a backup (From the Datastore -> Backups screen) it seems that we are unable to specify which pool to restore into. As users are not allowed to create VM's outside of their own pool(s) that results in an access-denied error. Allowing the VM.Allocate permission on the root, rather than specific pools, allows importing the VM's normally. However that's obviously not what we would want to do.
Are there better ways to restrict users to pools that still allows them to import backups? Or would this simply be a usecase that hasn't been implemented, requiring a pool-selection dropdown to be added to the Restore screen?
Thanks!