This will be likely effecting most, if not all, of your clients in the coming months, and thus is a very important request. It will make a massive impact on us - on whether we can still sell competitive Windows licensing on OnApp-based cloud VMs or no, so it is important for us to know over the coming month or two, will OnApp implement this or no. So, please kindly raise this internally and let us know.
Reason: Microsoft is changing its Windows SPLA licensing terms, whereby for VMs the customer must be charged for however many cores the largest HV has, regardless of how many cores the actual customer VM or resource pool has (i.e. regardless of how many cores the customer has access to). This means that a small 2 or 4 core Windows VM customer would still need to be charged for, say, 56 core Windows licensing (e.g. 28 times higher cost than it really "should be"), if the underlying HVs are 56 cores, to use an example. That will obviously send the customer packing and off to Azure, where Windows licensing is free. (Now you see why this is so very important.)
The only workaround is to use Microsoft Windows Data Center licensing, where we pay just one (rather high) flat fee per HV, and then the qty of VMs/customers using Windows on it become irrelevant. BUT, the issue with that is that for us, as probably for most other OnApp customers, Windows density is not that great. It's some 20~40% of the total OS usage. This only works if Windows density is 100% or close to 100% on the Windows DC SPLA licensed HVs. Setting up a separate Windows-only cloud doesn't work, as many customers have VMs of various OSes that they want within the same account, vs. to separate out Windows from Linux into two separate accounts (much harder to manage, more expensive also).
Feature Request: VM OS restriction implementation at the HV level. Simply put, ability to designate HVs, HV-by-HV, in any cloud by what OSes are permitted to run on the VMs being hosted on there. Available settings required:
* any OS (default; how it is now)
* Windows OS only (what would be used for Windows DC SPLA licensed HVs)
* any OS other than Windows (would be used for most HVs)
With the feature built, some additional OS restrictions may also be useful to your clients in other cases, e.g. RedHat Linux OS only, or better yet may be simply have the allowed OSes as checkboxes, where by default ALL are checked for each HV, but some can be unchecked...that would give the most flexibility.
Again, I can't stress the importance of this enough. Without this, we will lose most of our Windows OS using cloud clients, as will your other customers also, as a small VM customer is not going to pay 20 times more for the Windows license than they pay for the actual VM/resource pool, as will be the case now with this soon upcoming (Q2, 2018) SPLA licensing change, where the Windows licensing must be per core of the physical HV, regardless of how many cores the actual customer/VM has access to.