14 Responses

  1. jasonboche
    jasonboche at |

    Design decisions can fan in from a multitude of sources. Licensing is no different conceptually.

    I look at this as just another design decision where justification should be made and impacts identified (whether positive or negative). Initial indicators are that this new licensing model has an impact of higher cost for scale up environments. Conversely, know the impacts in the design decision of scaling out. That’s where we all just came from in the physical world. Datacenter buildouts. Real estate costs. Rack space. Heat. Cooling. Cabling. Depreciation. etc.

    Reply
  2. vSphere 5 introduction – Links « BasRaayman's technical diatribe
  3. Andrew Storrs
    Andrew Storrs at |

    Scaling out incurs a different licensing tax – namely Microsoft Windows Server Datacenter or RHEL per-socket licenses, as well as any 3rd party tools you may use (Quest, Veeam, vKernel) all of which are usually licensed per-socket (this may change now).

    Due to the changes with vSphere 5, we’re now forced to be extra skimpy with initial allocations of memory (rather than throwing physical RAM at the hosts and not fighting that political battle). At least with the latest O/S’s (Win2k8, etc) we can dynamically hot-add memory without rebooting (whether the app detects the change is another story).

    The VMs that just became very expensive are those that had large amounts of cache (databases, web application servers, messaging servers).

    My 2¢

    Reply
  4. Hugo Peeters
    Hugo Peeters at |

    Here’s a script to help you calculate license requirements for vSphere 5:
    http://www.peetersonline.nl/index.php/vmware/calculate-vsphere-5-licenses-with-powershell/
    Hugo

    Reply
  5. VMware vSphere 5 licensing: the opinions and math | UP2V

    […] vSphere 5 Licensing Model – Death to Scaling Up?  by Chris Wahl […]

  6. John Troyer / VMware
    John Troyer / VMware at |

    Chris, you’ve got a good discussion going here, so I don’t want to nitpick, but since it does come down to the numbers — for this theoretical cluster, are you running all 6 machines at 100% CPU utilization? Remember vRAM != pRAM. Also, in your environment, do you have other clusters or machines that are not as heavily utilized that could add to the vRAM pool?

    This new licensing *is* intimately connected with your *total* real world design. Calculations on isolated physical components may not proportionately reflect the total cost. Already your cost with 6+1 cluster design looks different from looking at a single server.

    Reply
  7. wuffers
    wuffers at |

    How do the new vRAM entitlements affect you?

    Please take 2 minutes of your time to fill out this vSphere 5 migration survey:
    http://wuffers.net/2011/07/18/vsphere-5-migration-survey

    We need more data! Results will be posted in the main vSphere 5 licensing thread over at VMTN:
    http://communities.vmware.com/thread/320877

    First round of results here: http://communities.vmware.com/message/1795012#1795012

    Reply
  8. AD
    AD at |

    Dear all… the information i have from VM site is that it supports 96 GB per CPU with Enterprise Plus…

    http://www.vmware.com/files/pdf/vsphere_pricing.pdf

    I am not sure where is 48 GB per CPU mentioned… can you please refer to any official link.

    Reply

Share your point of view!