Virtualization, Cloud, Infrastructure and all that stuff in-between

My ramblings on the stuff that holds it all together

VMware Licensing for the vCloud..


I have been involved with VMware’s vCloud programme since it was announced late 2008, I was part of getting involved as one of a handful of partners on the launch-day and I have been doing private cloud work with customers since early 2008.

Whilst I was somewhat disappointed that as a smaller partner we were left out as VMware pressed on with the major partners and availability of information and tools were limited, it did eventually evolve into a set of emerging technology and products that we got access to.

One part of this that has troubled me for some time is licensing of VMware products for cloud/IaaS offerings, as an accredited VMware hosting provider we have access to service provider licensing (SPLA) for VMware products.

The concept of SPLA is simple, it’s a monthly rental of a product – the core VMware products being ESX and vCenter; the hoster pays VMware a monthly fee based on the peak number of virtual machines running in that month regardless of how many ESX installations/sockets/cores there are – this is a simple cost model for a hoster as the general unit of charging for an end-customer is a virtual machine over a period of time (the cost of which is made up of a slice of the supporting hardware/software/service-level).

As a service provider you want to minimise capital expenditure wherever possible, particularly when it comes to a cloud/IaaS model as there is often no long-term contractual  commitment for a customer, if they need 100 VM’s one month and 2 the following it’s your burden as a service provider to provide {via investment} that infrastructure and software; for smaller/niche/private cloud players this is an issue – unless you have a large-scale and diverse customer base this is a risky operation and often breaks the cloud business case for the end-customer as the provider has to build in recovery of investment.

Amazon do well in this space with EC2 because they have massive scale and diversity of customers across all industry sectors so most peaks and troughs of demand average out in the bigger picture (see: commoditization and utility – Nicholas Carr’s book “The big switch” covers this well, as does Cannonical’s Simon Wardley at various Cloudcamps)

In my experience this is a problem right now for service providers looking to build cloud services on vSphere/vCloud as very few of VMware’s ancillary products are available on their hosted/SPLA licensing scheme, last time I enquired it it is limited to ESX, View, vCenter and I believe SRM has recently been added.

Also, companies looking to build internal cloud services can only leverage this SPLA type of licensing when the service is hosted and resold from a service provider’s own data centre & infrastructure, rather than customer hosted equipment – this protects the revenue stream of service providers, but does it harm the longer term private cloud prospect, particularly with customers that have a regulatory or security need that prevents traditional outsourcing/hosting?

There are a number of products that would be ideal for cloud/IaaS providers to better manage and control their services, but these are currently only available on a perpetual basis with traditional per CPU socket licensing – this perpetual model is hard for smaller/niche service providers where the capacity planning cycle continually looks for ways to deliver the required service with less infrastructure or have requirements to re-provision servers between physical and virtual instances, or where kit is leased/rented to cover short-term projects and demands.

The products that I see being ideal for service providers, if they could be offered on a SPLA basis rather than perpetual are;

  • AppSense – this is almost a no-brainer; its a great way to manage end-end SLA for application delivery in a cloud platform.
  • Cisco NX1000V – most service providers have big, highly skilled network teams and complex multi-customer environments to manage; this is ideal Nexus territory
  • Chargeback – although I understand this is being built into the vCloud billing services, this has been available now for a while, and is a workable product to build billing systems.
  • Lab Manager – some of the tech seems to be getting merged into the vCloud services at some level, but self-service lab environments in a private-cloud scenario with some control over VM lease/retention is something people have been asking for.
  • CapacityIQ – designed for balancing load and capacity, important to a multi-tenant environment
  • ConfigControl (licensing not announced) – but you can definitely see the need for this in a large multi-tenant environment

Microsoft, to their credit have this absolutely nailed; their SPLA licensing model is very mature and has all the products from their vast catalogue, even if the Service Provider Usage Rights (SPUR) documents can get a bit complicated to read/digest, VMware have moved to a similar contractual model via resellers for the latest iteration of their hosted license agreement with a more flexible model to add products; but it’s not there yet.

Whilst from a commercial point of view SPLA licensing doesn’t have the “big deal” values in terms of upfront revenues to VMware’s sales force it’s a constant revenue stream, and generally everyone accepts that SPLA will be more expensive than perpetual licensing over a given period; but the increased cost reflects the flexibility/lack of commitment advantage.

Interestingly, it also makes it easier for service providers (and thus customers) to deploy VMware products in their own hosting platforms – easier to build a business case, less upfront sizing/capacity planning & forecasting, costs for growth are incremental and pure op-ex (it’s almost like a cloud within a cloud!).

So, by way of conclusion – whilst a lot of the products I’ve previously desired on SPLA (lifecycle manager, lab manager, Chargeback etc.) are being merged into the vCloud  “product” for service providers VMware should consider offering everything on a SPLA basis to hosters, and maybe even consider such a licensing scheme for customers own internal usage to bolster the private cloud model.

8 responses to “VMware Licensing for the vCloud..

  1. Rodos April 8, 2010 at 12:25 pm

    Great post. However I can’t agree that Microsoft have nailed their SPLA licensing. The SPUR is difficult and its not that easy to use in a Cloud environment. IMHO

  2. vinf April 8, 2010 at 9:38 pm

    Thanks Rodos, I think MS have nailed the fact that you can license /all/ their products on a SPLA basis and choose a per-vCPU basis or per host/VM/User model where it makes more sense – VMW have some way to go to do this for their products.

    The SPUR is complicated but there is a tool to produce a document with only the sections relevant to the products you are deploying, it’s good to have a defacto document to refer to. but there are a lot of clauses that differ between perpetual and SPLA and things like SA and DR usage are a bit unclear on SPLA.

    MS SPLA is also a minimum monthly unit of sale, same as VMware’s VSPP; so if it’s an EC2 type use-case where you want those instances for days, or even hours; it’s not as good.


  3. Pingback: ACADIA…thoughts « Virtualization, Windows, Infrastructure and all that “stuff” in-between

  4. Mark Hodges July 7, 2010 at 1:06 am

    Actually, MS has absolutely no minimums on SPLA – I’ve used as low as 5 licenses in a month.
    The last I looked at vmware VSPP it was based on levels (and at $35/server (enterprise environment), pretty much puts them out of the price contention with anyone else)

    Where Microsoft is really screwing all of us service providers is in the VDI space.
    Here is an official response from Microsoft SPLA group below. The highlight is:

    The end customer must have a valid license for every server and server product they access – forget shared gateways, Active directory, file services,etc. EVERYTHING must be isolated for that customer and licensed under the customers MVLS license agreement.
    Great F’n job Microsoft…

    Here’s the most up-to-date MS response (July 2010):

    Q: Is VDI/VECD/MED-V available in SPLA or HVS?
    A: No. Virtual Desktop Infrastructure (VDI) with Windows desktop OS is possible with Windows Vista Enterprise Centralized Desktop (VECD) under Microsoft’s internal-use Volume Licensing programs (such as Open, Select and EA) but it is not enabled or available under SPLA or HVS at this time.

    Q: How can I enable my hosting partner to offer VDI services to SMB customers?
    A: Since VDI with Windows desktop OS is not supported in SPLA/HVS, hosting partners can only offer Windows VDI deployments to their customers through an outsourcer arrangement under the end customer’s Volume Licensing agreement (if available) by having their end customers acquire their own perpetual licenses for VECD and allowing the service provider to manage those licenses on their behalf. In this scenario, it’s important to remember the following:
    – Licenses belonging to the end customer cannot be shared among other customers of the service provider; this means that end customer owned licenses cannot be used in shared hosting environments (where more than one customer accesses a server). They can only be used in dedicated environments (where one server is dedicated to a particular end customer)
    – The end customer must have a valid license for every server and server product they access (including access licenses such as CALs). For example, if the end customer accesses 2 servers that have Windows & SQL installed on them, they would need the appropriate number of Server and CAL licenses for each of those servers.
    – No mixing/matching of server/CALs on a product-by-product basis. This means that end customer CALs for a particular product cannot be used to access servers deployed with that product and which are licensed by the service provider under SPLA. It also means that if an end customer has Servers/CALs for a particular product(s) and chooses to move to a hosted model with a service provider, they will need to acquire any additional licenses for that product(s) under their volume licensing agreement (i.e. if they increase the number of seats or require more servers for a built out for deployment or load balancing). It’s not ok for the service provider to acquire SALs under SPLA when the number of seats goes up for the end customer or when additional servers are required. This is because the licensing construct of internal use doesn’t match that of SPLA and therefore needs to be kept separate.

    Q: Is there any possibility that VECD will be licensed under SPLA/HVS in the future?
    A: We are currently working with the product groups to identify scenarios for VECD in SPLA and it’s possible this is something that may be added in the future though there is no commitment at this time

  5. Pingback: Top Virtualization Blog Voting Time « Virtualization, Windows, Infrastructure and all that stuff in-between

  6. Pingback: That was 2010 so what next « Virtualization, Windows, Infrastructure and all that stuff in-between

  7. Pingback: Killing vRAM is a backward step « Virtualization, Cloud, Infrastructure and all that stuff in-between

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: