At Inovativ, the company I work for, we more or less use Windows Azure Pack in production now. We have begun to operate as a hoster and each consultant is a tenant in our Inovativ Cloud. They can go to the Windows Azure Pack tenant portal and consume the resources we have available in our cloud. If you don’t set any rules your tenants are likely to grab all the resources that are available. Currently we have not yet set any quotas, but I’m afraid we will have to very soon.
One problem that we encountered was that VMs which were created outside of the portal did not have the correct Owner and User Role. This would mean that those VMs were not visible as owned by a certain tenant in the Windows Azure Pack tenant portal. Also when you set quota on for instance the number of VMs that could be created or the amount of memory that could be consumed, only the VMs were counted that were actually owned by the tenant.
This would be a serious problem if you are a hoster an wanted to move existing VMs to a tenant’s subscription or service plan as it is called in Windows Azure Pack. Another problem that we think is linked to this is that Cloud Cruiser which collects usage information for billing or showback is not able to process the usage records.
This is what it looks like from the admin portal when you go to VM Clouds and find all VMs for a certain tenant and subscription to a tenant plan. As you can see there not all of my VMs are listed.
It was quite easy to give access to the manually added VMs via the VM properties in Virtual Machine Manager 2012 R2. The first requirement is assign the VM to the same VMM Cloud that is used in Windows Azure Pack. If the VM does not have an Self-Service owner, you can select one. The problem however is that the only accounts you can choose are Active Directory accounts. This is exactly what we don’t want.