VMware vSphere Distributed Switch (VDS) is a key virtual network platform that is scalable and extensible. It also provides advanced networking features and operational simplicity that helps build a flexible network for the cloud. The advanced networking features such as NIOC, LBT, NetFlow, and Port mirror are available on VDS and not on a virtual standard switch (VSS). This paper walks through the design process of incorporating VDS and its advanced features in different customer deployments. Customers typically have various types of server hardware and network adapter configurations in their environment. Following standard server hardware configurations are considered during the VDS design discussions.
1) Rack Server with Eight 1 Gigabit network adapters
2) Rack Server with two 10 Gigabit network adapters
3) Blade Server with two 10 Gigabit network adapters
4) Blade Server with Hardware assisted multiple Logical network adapters
For all these above hardware configurations different VDS design approaches will be presented along with their pros and cons. Along the way some best practices and important parameters of virtual and physical switches will be highlighted. Finally, some operational aspects of the VDS will also be discussed.
One of the cool new features of vSphere 5 is Auto Deploy. This tool enables the stateless booting of ESXi hosts. No longer a installation to disks is required to boot the ESXi hypervisor. Instead the hypervisor is booted via PXE boot into the memory. The ESXi image is booted onto a bare-metal server, so in case the server powered off the “installation” and configuration is also lost. Of course the next time the bare-metal server is booted up again, Auto Deploy makes sure that the stateless image is again deployed via PXE into the memory of the server. So far, so good. If of course the Auto Deploy tool is available to provide the deployment of ESXi images.
And this is the question that always pops up when discussing Auto Deploy in a vSphere design: “What if the Auto Deploy tool isn’t available? Then I can’t boot my ESXi hosts anymore!”
That is true, but fortunately there is a way around that. Daniel Hiltgen, Senior Staff Engineer at VMware, explains how to architect your Auto Deploy environment and make it highly available. This also prevents the “chicken-egg” problem. So have a quick look at this short, but interesting video!
At some points in life you look back on your career and think “What can make my working life more interesting and more challenging?” Well over the last year I’ve been asking myself this question, searched for it, talked to a lot of people and finally came to the answer.
And today, the 31st of August 2011, is the day I can announce to everybody what my answer is:
On the 1st of October I will be joining VMware (PSO) as Senior Consultant !
I’m really looking forward to working with the great minds in the field of virtualization and cloud computing.
And I would like to thank everybody who was involved in the process of me moving toward VMware. Thanks for the effort and the support!
So it has been a while since the announcement last month, but finally it’s available for download : vSphere 5! VMware again raised the bar an created the next generation in cloud computing / virtualization software. And with VMworld just around the corner, everybody can now experience the true power of VMware’s nextgen cloud OS.
So what’s in this new release? Where to start. VMware has improved a lot of features that where also available in vSphere 4.1, but also included a lot of new features that make vSphere more and more a flexible and dynamic cloud OS. With more then 140 new features this sure is a masterpiece of work by VMware.
To get more information about the new release have a look over here at the following links :
VMware announced an update in the licensing for vSphere 5. There has been a lot of discussion. Especially about the introduction of vRAM as a limitation to the amount of VMs you can deploy. It’s good to see that VMware is open for discussion about their licensing change and has taken the reactions of customers and partners about it in consideration.
This change isa the result of some good discussion about the vSphere 5 licensing change. In my opinion these new vRAM entitlement are a better representation of the 90% of customers, the amount that VMware was targeting, that should not be affected by the licensing change. This makes it possible for most vSphere 4 customers to migratie to version 5 without having to buy extra licenses and I think that was the message that came out of the discussion between VMware, its customers and its partners.
These are the changes made by VMware with regards to licensing :
An increased vRAM entitlements for all vSphere editions, including the doubling of the entitlements for vSphere Enterprise and Enterprise Plus. This change addresses concerns about future-looking business cases that were based on future hardware capabilities and the previous vSphere licensing model. Below is a comparison of the previously announced and the new vSphere 5 vRAM entitlements per vSphere edition:
vSphere Edition
Previous vRAM entitlement
New vRAM entitlement
vSphere Enterprise+
48 GB
96 GB
vSphere Enterprise
32 GB
64 GB
vSphere Standard
24 GB
32 GB
vSphere Essentials+
24 GB
32 GB
vSphere Essentials
24 GB
32 GB
A capped amount of vRAM is counted in any given VM, so that no VM, not even the “monster” 1TB vRAM VM, would cost more than one vSphere Enterprise Plus license. This change also aligns with our goal to make vSphere 5 the best platform for running Tier 1 applications.
An adjusted of the model to be much more flexible around transient workloads, and short-term spikes that are typical in test & development environments for example. We will now calculate a 12-month average of consumed vRAM to rather than tracking the high water mark of vRAM.
For more information see the blog post on the VMware partner blog site here.
Looking into the new features of vSphere, Storage Distributed Resource Scheduler (SDRS) is probably one of the best and one of the coolest new features that comes with vSphere 5. DRS is one of the standard features in vSphere and is used to distribute the load of the workload evenly over all the ESXi host within a cluster.
Within vSphere 4.1 and previous versions this was based on the CPU and memory load which was generated by the virtual machines that were hosted on top of vSphere. Now with vSphere 5 VMware has added Storage DRS. This extends DRS with the storage stack.
Storage DRS provides smart virtual machine placement and load balancing mechanisms based on I/O and space capacity. Overall this comes down to four nice features that Storage DRS provides :
1. Smart initial placement of the VMDK on the LUNs
2. Migration recommendations (manual and automated)
3. Affinity and anti-affinity rules
4. Storage maintenace mode
Basically these features are similar to the features you see with “normal” DRS. It adds a whole new dimension to vSphere and makes it more flexible and contributes to the fact that vSphere is a cloud operating system. In my opinion this will make life a lot easier and in the end it will save time and money in operating your virtual infrastructure.
To see how Storage DRS in action, have a closer look at the following video created by VMware :
For more information on the topic of Storage DRS see :
And if you really want to dive into the new features of DRS, including Storage DRS, you have to take a look at the book written by Duncan Epping and Frank Denneman : VMware vSphere 5 : Clustering Technical Deepdive.
VMware releases a new vSphere License for the hosting of VDI desktops. In addition to the new vSphere 5 licensing editions, VMware releases a new edition : vSphere Desktop : vSphere Edition to host Desktop Virtualization
vSphere Desktop is a new edition of vSphere for deploying desktop virtualization. It provides the full range of features and functionalities of the vSphere Enterprise+ edition allowing you to achieve scalability, high availability and optimal performance for all of your desktop workloads.
Also, vSphere Desktop enables you to realize high virtual desktop consolidation ratios at a lower cost as it comes with unlimited vRAM entitlement. The vSphere Desktop edition is intended for customers who want to purchase only vSphere licenses to deploy desktop virtualization. In addition to the vSphere Desktop edition, VMware also sells a comprehensive end to end desktop and application virtualization solution – VMware View.
vSphere Desktop is already included in the View Bundle – The desktop and application virtualization product from VMware. This offer gives customers the option to purchase vSphere Desktop as a standalone vSphere edition outside of the View Bundle.
vSphere Desktop is licensed based on the total number of Powered On Desktop Virtual Machines. It is available in a pack size of 100 desktop VM at a license list price of $6500 USD.
vSphere Desktop can be used only for hosting a VDI environment.
The article below also gives a good example on how this new edition impact licensing cost in contrast to vSphere Enterprise Plus license.
vSphere Desktop is the cost effective vSphere SKU for deploying desktop virtualization.
Example: Customer deploying 1000 Win 7 desktops
Assumptions:
Memory/VM =1 GB
vSphere Ent+: List Price: $3495/CPU with vRAM
entitlement of 48GB
vSphere Desktop: List Price $65/VM, Unlimited vRAM
entitlement for desktop VMs
# of vSphere Enterprise+ licenses required = (Total pooled vRAM required for all desktop VMs / MIN (vRAM used per processor, vRAM entitlement per processor)) = (1000 desktop VM *1GB / MIN (vRAM entitlement used,48GB) )
# of vSphere Desktop licenses required = # of desktop VMs
The release of VMware vSphere 5 comes with a new licensing model. This model is based on licensing “per CPU with vRAM entitlement limitation”. As I mentioned in my previous licensing post this is a difference with regards to the previous vSphere version. :
“Also I need to mention that VMware changed it’s licensing model from a “per CPU with core / physical memory” to a “per CPU with vRAM entitlement limitation”. No longer the limitation is on the amount of cores or physical RAM memory in a server, but the limitation is in the amount of virtual memory (vRAM) consumed by the hosted virtual machines.”
In this post I will try to explain the per CPU with vRAM licensing model by using the example below. I hope this will make things a lot easier to grasp. After all it’s about licensing, so it’s about money! And in the end you don’t want to end up in a situation that you’re unable to power-on new virtual machines.
In the example we have 2 ESXi host that both have 2 processors. The amount of cores does not matter anymore when using vSphere 5. There is no longer a limitation on the amount of cores or the amount of physical memory in a server. But as mentioned above, VMware has introduced a new limitation with regards to licensing : vRAM entitlement.
vRAM entitlement
vRAM entitlement comes with each “per CPU” license. The amount of vRAM depends on the vSphere edition that is being used.
* vSphere 5 Standard Edition gives you 24 GB vRAM
* vSphere 5 Enterprise Edition gives you 32 GB vRAM
* vSphere 5 Enterprise Plus Edition gives you 48 GB vRAM
So this means that for each CPU license that you buy, you’ll get a certain amount of vRAM entitled. In the example above there are 2 physical CPUs in each ESXi host. Making a total of (2 x 2 = ) 4 physical CPUs you’ll need to license for VMware vSphere 5. In the example I’m using Enterprise licenses, which entitle me to 32 GB of vRAM per CPU license. This makes a grant total of 128 GB of vRAM which I can use.
The total vRAM is also known as a vRAM entitlement pool. This is the combined total of all the ESXi hosts managed by a vCenter instance or a set of linked vCenter instances. Every vRAM entitlement is aggregated into one pool which can be used by all virtual machines managed by vCenter.
vRAM usage
The usage of vRAM comes with the amount of virtual machines that is powered-on. Each time a virtual machines is powered-on, licensing will check if enough vRAM is available in the vRAM pool. The amount of vRAM used by the virtual machine is then added to the total amount of vRAM used by all virtual machines combined.
The total of the used amount of vRAM must be equal of lower then the total amount of vRAM in the vRAM pool. If this is not the case, the virtual machine will not be powered on and you’ll need to buy more licenses or upgrade to a higher vSphere Edition (if possible).
In the example above we have 18 virtual machines, all configured with different amounts of vRAM per virtual machine. The total amount of vRAM used by all virtual machines is 68 GB.
Summary
So looking at the example again. I’ve got 128 GB of vRAM in my vRAM pool. At this moment I’ve got 18 virtual machines that combined have a vRAM usage of 68 GB.
So to calculate the amount of vRAM I still have left I need to take total licensed vRAM minus the vRAM that is already used by the virtual machines :
Total licensed vRAM – Used vRAM = Available vRAM
In the end this comes down to 128 GB (Total licensed vRAM) – 68 GB (Used vRAM) = 60 GB of vRAM that still available for new “to-be-powered-on” virtual machines.
I hope this gives a good impression of how the vRAM entitlement works in vSphere 5. For more information have a look at the VMware vSphere 5 Licensing, Pricing and Packaging Whitepaper over here.
Update : PowerCLI guru Luc Dekens already wrote a Powershell scrip to verify if your vSphere environment is covered by the new vRAM licensing model. See for yourself over here.
With the new vSphere release VMware also updated the licensing for this release. The diagram below gives a graphical representation about what features are included per vSphere edition.
As you can see VMware will release vSphere 5 into 3 Editions : Standard, Enterprise and Enterprise Plus. These can be bought individually, but can also be purchased in Acceleration Kits which will give you a fixed amount of vSphere CPU / vRAM licenses and a vCenter license for a standard price out of the box.
Also I need to mention that VMware changed it’s licensing model from a “per CPU with core / physical memory” to a “per CPU wit vRAM limitation”. No longer the limitation is on the amount of cores or physical RAM memory in a server, but the limitation is in the amount of virtual memory (vRAM) consumed by the hosted virtual machines.
Besides the vSphere Editions you can also buy the (SMB) Essentials kits. These are specifically targeted at small businesses. Not all vSphere features are included in these releases, but enough to run your SMB workloads.
For more information about licensing and how to obtain vShere 5 over here.
Today Paul Maritz and Steven Herrod announced the release of VMware vSphere 5. This release is the next step in VMware’s cloud operating system. It is the industry leading platform for building cloud infrastructures.
vSphere accelerates the shift to cloud computing for existing datacenters, while underpinning
compatible public cloud offerings, paving the way to the only hybrid cloud model.
New Features include :
Scalability and Performance – Enables Virtual Machines (VM) to grow up to 32 virtual CPUs, can support 1TB vRAM, and a variety of next-generation hardware, such as 3D graphics processors and USB 3.0 devices.
High Availability – Deliver the right availability services with groundbreaking simplicity for any application.
Auto-Deploy – Deploy more vSphere hosts running the ESXi hypervisor architecture in minutes.
Flexible Hybrid Cloud Management – The vCenter Server Appliance is a Linux-based virtual appliance and the Web Client works from any browser anywhere in the world.
From my point of view this release is again a major (r)evolution in path towards a cloud operating system that can be used for both private as public clouds. vSphere is the base for all the VMware products and indeed like the online event suggested VMware raises the bar again for the competition to follow. This results in a cloud operating system which more and more becomes hardware independent. Which in the end will make IT infrastructure a lot more flexible and easier to maintain.
More information about VMware vSphere 5 is available over here.
