Hello,
Maybe someone can help us with the following...
We have quota policies with limits applied to the users, some VMs are being onborded as part of a migration process. When the VMs are onboarded and assigned to the owner the quota limit is not being applied. If the quota limit is 3 vCPU and the VM migrated has 6 vCPU the VM will be onboarded regardless of the quota limits. I believe that by design that's expected since the onboard process will not check the DB, and won't be able to be aware of the restrictions that we have in place for that owner.
Here's the issue:
When the onboard process completes the VM gets assigned to owner, ie. user1 and will be registered in the DB with ownership, etc.
When "user1" creates an additional requests from vRA8 and has an exceeded quota because of the onboarded VMs (it has 6vCPU) the quota limit restriction does NOT apply again the user is able to create a new request (he should not because the owner has already a VM with 6 vCPU's assigned to him).
For example Quota Policy max vCPU3
owner - user1 - 6 vCPU VM1 has been onboarded (this is done externally by an admin)
owner - user1 - The user himself creates a 2 vCPU VM2 from vRA8 and is able to do it. He should not because VM1 has 6 vCPUs and it's owned by him already.
Is there any way, once the VM onboarding completes and the VM is assigned to an owner as part of that process to have vRA8 be aware of the resources assigned to that VM that are assigned to an owner and apply quota limits correctly?
