View
554
Download
3
Tags:
Embed Size (px)
DESCRIPTION
Citation preview
© 2009 VMware Inc. All rights reserved
vSphere 5 Licensing and Packaging
VMware, August 2011
2
vSphere 5 licensing: Evolution Without Disruption
vSphere 4.x vSphere 5
Licensing Unit Processor = Processor
Core per proc Restricted < Unlimited
Physical RAM
per host Restricted < Unlimited
Pooled vRAM
entitlement NA ≠
Amt of vRAM pooled
across entire
environment
!
3
What is vRAM?
vRAM is the memory configured to a virtual machine
Assigning a certain amount of vRAM is a required step in the
creation of a virtual machine
4
Key vRAM Concepts
Pooled vRAM Entitlement
Each vSphere 5 processor license comes with certain
amount of vRAM entitlement
Sum of all
processor license
entitlements Consumed vRAM
Sum of vRAM
configured into all
powered on VMs
1
2
3
Compliance =
12 month rolling average of Consumed vRAM < Pooled vRAM Entitlement
4
5
Key concepts - Example
Host A
1 1
vSphere Ent
1 1
vSphere Ent
CPU CPU CPU CPU
Host B
64GB 64GB 64GB 64GB
vRAM Pool (256GB)
Consumed vRAM = 80 GB
4 licenses of vSphere
Enterprise Edition
provide a vRAM pool of
256GB (4 * 64 GB)
Customer creates
20 VMs with 4GB
vRAM each
Each vSphere Enterprise
Edition license entitles
to 64GB of vRAM.
Compliance =
12 month rolling average of Consumed vRAM < Pooled vRAM Entitlement
6
vSphere 5 Licensing
Detail
7
vSphere 5.0 Licensing Model in More Detail
vSphere 4.1 and prior
Per CPU with Core and Physical
Memory Limits
vSphere 5.0 and later
Per CPU with
vRAM Entitlements
Licensing Unit CPU = CPU
SnS Unit CPU = CPU
Core per proc Restrictions by vSphere editions • 6 cores for Standard and Enterprise, Ess, Ess+
• 12 core for Advanced and Ent. Plus < Unlimited
Physical RAM
capacity per host
Restrictions by vSphere edition • 256GB for Standard, Advanced and Enterprise.
Ess, Ess+
• Unlimited for Enterprise Plus
< Unlimited
vRAM entitlement per
proc Not applicable ≠
Entitlement by vSphere edition • 32GB vRAM for Essentials Kit
• 32GB vRAM for Essentials Plus Kit
• 32GB vRAM for Standard
• 64GB vRAM for Enterprise
• 96GB vRAM for Enterprise Plus
Pooling of entitlements Not applicable < YES – vRAM entitlements are pooled
among vSphere hosts managed by a
vCenter or linked vCenter instance
Max amount of vRAM per
VM counted Not applicable ≠
96GB – a powered on VM will count for a
maximum of 96GB against the pool
regardless of its actual configured amount
Compliance policies • Purchase in advance of use
• High Watermark =
• Purchase in advance of use
• 12 months rolling average of daily
high watermark
Monitoring tool Not applicable ≠ YES – built-into vCenter Server 5.0
8
vRAM Pool
(using 80 GB out of 256GB)
vSphere 5 Licensing In Action
Each CPU must have at least one vSphere license
assigned
• Cores and physical RAM do not matter
Each processor license managed by a vCenter or
multiple vCenters in Linked mode contributes an
amount of vRAM capacity to the total vRAM pool
• Example: 4 vSphere Ent. Licenses create a vRAM pool
of 256GB of vRAM (4 x 64GB)
• Each vSphere Edition creates a separate pool that
must be kept in licensing compliance
vRAM pool is shared among powered-on VMs
running on all hosts in a vCenter
• Example: 20 VMs with 4GB of configured vRAM
consume a total of 80GB vRAM
• It doesn’t matter how many VMs you run and on which
hosts you run them.
• vMotion, DRS, HA do not require additional licenses
At any point in time the 12 month rolling average of
daily high watermark of consumed vRAM must be
equal or less to the vRAM pool capacity
• Compliance is at the vCenter level not the host level
vRAM pool can be extended by:
• Upgrading all CPUs to higher end vSphere Edition
• Adding processor licenses to the same set of CPUs
• Adding a new host with new licenses
VM (4GB vRAM)
1
Processor License
Host A
1 1
vSphere Ent
1 1
vSphere Ent
CPU CPU CPU CPU
Host B
VMware vCenter Server
vSphere 5.0 How does it work?
9
Tools for Tracking vRAM Entitlement vs Usage
Before upgrading to vSphere 5, customers can use a
separate free utility that analyzes a VI3 or vSphere 4
environment, and determines vRAM consumed • The tool will be available later in Q3 2011
After upgrading to vSphere 5:
1. vRAM licensing monitoring and reporting tool built into vCenter 5
2. Free add-on to vCenter for in-depth historical trending analysis
10
When Does the vSphere 5 Licensing Model Apply?
For ELA customers
Customers with active ELA will continue to be subject to the terms of their
contracts for the duration of their contract, independent of which vSphere
version they deployed
• ELA customers may contact their VMware sales representatives to update the
terms of their ELAs to the new vSphere 5 licensing model
For customers without ELAs
The new model applies only to vSphere 5 licenses. Prior versions of
vSphere will continue to be based on their respective licensing model
The new vSphere 5 licensing model will apply upon acceptance of the
vSphere 5 EULA (necessary condition to upgrade to vSphere 5)
Customers who purchase vSphere 5 licenses and decide to downgrade to
older versions of vSphere will be subject to the EULA terms and licensing
model of the vSphere version they downgrade to
11
vSphere 5 Packaging
12
All editions include: Thin Provisioning, Update Manager, Storage APIs for Data Protection, Image Profile, and SLES (except Ess and Ess +)
` Essentials Essentials
Plus Standard Enterprise
Enterprise
Plus
vRAM Entitlement per proc 32 GB 32GB 32 GB 64 GB 96 GB
vCPU 8 way 8 way 8 way 8 way 32 way
Features
Hypervisor
High Availability
Data Recovery
vMotion
Virtual Serial Port Concentrator
Hot Add
vShield Zones
Fault Tolerance
Storage APIs for Array Integration
Storage vMotion
Distribute Resource Scheduler &
Distributed Power Management
Distributed Switch
I/O Controls (Network and Storage)
Host Profiles
Auto deploy
Profile-Driven Storage
Storage DRS
Essentials Essentials
Plus Standard Advanced Enterprise
Enterprise
Plus New in vSphere 5.0
vSphere Storage
Appliance
+
vSphere 5 Editions
13
Entitlements per CPU license
• vRAM Entitlement 32 GB
(192 GB max) 32 GB
(192 GB max) 32 GB
(256GB per kit) 64 GB
(384 per kit) 96 GB
(576 per kit)
• vCPU 8 way 8 way 8 way 8 way 32 way
Features
Hypervisor
High Availability
Data Recovery
vMotion
Virtual Serial Port Concentrator
Hot Add
vShield Zones
Fault Tolerance
Storage APIs for Array Integration
Storage vMotion
Distribute Resource Scheduler &
Distributed Power Management
Distributed Switch
I/O Controls (Network and Storage)
Host Profiles
Auto deploy
Profile-Driven Storage
Storage DRS
All editions include: Thin Provisioning, Update Manager, Storage APIs for Data Protection, Image Profile, and SLES (except Ess and Ess +)
Essentials Essentials
Plus
Standard
AK
Enterprise
AK
Enterprise
Plus AK New in vSphere 5.0
vSphere 5 Acceleration Kits
14
Entitlement Paths for current vSphere 4.x customers
vSphere 4.x vSphere 5.0
Enterprise Plus
Enterprise
Advanced
Standard
Essentials Plus
Essentials
Enterprise Plus
Enterprise
Standard
Essentials Plus
Essentials
15
Upgrade Paths for vSphere Editions and Kits
Enterprise
Standard
Enterprise Plus
Enterprise Plus
Enterprise
Essentials Plus
Essentials
Any one of the Acceleration Kits
Essentials Plus
Any one of the Acceleration Kits
16
VMware vSphere Hypervisor 5
Full-featured hypervisor
Based on VMware’s next generation hypervisor architecture, ESXi
Provides the same performance, reliability and robustness of the
ESXi included with paid versions of VMware vSphere
Basic virtualization capabilities for a single host
Cannot be centrally managed with vCenter Server
Individual vSphere Hypervisor hosts can be remotely managed
with the vSphere Client
Provides only basic server consolidation capabilities
Free
Entitles to 32GB of vRAM per server and can be used on servers
with up to 32GB of physical RAM
Can be easily upgraded to paid vSphere editions for central
management and advanced capabilities
Entry level free product for single server virtualization
17
vSphere Storage Appliance 1.0
Packaging
18
vSphere Storage Appliance - Shared Storage for Everyone
Five click simplicity
Install in minutes
Easy to use
Saves money 1
High Availability without
the need for shared
storage hardware
Survive server failures
No more planned
downtime
2
Set and forget
automation
Get more out of your
hardware
World-class datacenter
capabilities – even for
small environments
3
vSphere Storage Appliance
Licensing
Shared storage capabilities,
without the cost and complexity
vSphere Storage Appliance
Per instance
(up to 3 nodes)
vSphere Storage Appliance
available at cost down
when purchased with
vSphere Essentials Plus
vSphere Essentials Plus w/
vSphere Storage Appliance +
19
VMware vCenter
Site Recovery Manager 5.0
Packaging
20
SRM 5 Editions Lineup
SRM 5
Standard Enterprise
Scalability Limits
• Maximum protected VMs 75 virtual machines (1)
Unlimited(2)
Features
• Support for storage-based replication
• Centralized recovery plans
• Non-disruptive testing
• Automated DR failover
• vSphere Replication
• Automated failback
• Planned migration
New in SRM 5.0 1. Maximum of 75 VMs per site and per SRM instance
2. Subject to the product’s technical scalability limits
US pricing only. Pricing outside the US might vary
21
vSphere 5.0 Licensing -
Detailed Examples
22
Customer Scenario
How do I license a host with vSphere 5?
How much vRAM do I get with my vSphere 5 licenses?
What is the vRAM pool?
How many VMs can I run with my vRAM pool?
How many VMs can I power on a host?
What if my VMs move to a different host with vMotion or DRS?
What is my vRAM pool if I have multiple vCenter Servers?
What is my vRAM pool if I have more than one vSphere edition?
How do I expand my vRAM pool?
How do I license an new host and join it to my vRAM pool?
What are the benefits of the vSphere 5 licensing model?
Will vSphere 5 be more expensive for vSphere 4.x customers?
23
How Many vSphere Licenses Do I Need?
Host A
1 1
vSphere Ent
1 1
vSphere Ent
CPU CPU CPU CPU
Host B
VM (4GB vRAM)
Powered-off VM
1
Processor License
In this example:
• Licensing Host A with vSphere 5 requires the
same number of licenses as with vSphere 4.x
• Licensing Host B with vSphere 5 requires half
the licenses of vSphere 4.x (2 vs. 4) because
vSphere 5 does not limit the number of cores
per processor
Answer
Example
Host A 2 sockets, 4 cores per CPU, 48GB RAM
Host B 2 sockets, 12 cores per CPU, 64GB RAM
Like in vSphere 4.x, each CPU requires at
least one license
vSphere 5 licensing does not impose limits
on number of cores per processor and
physical RAM per server
Summary
Hosts 2
CPUs 4
vSphere Licenses 4
24
How Much vRAM Do I Get with My vSphere Licenses?
Host A
1 1
vSphere Ent
1 1
vSphere Ent
CPU CPU CPU CPU
Host B
VM (4GB vRAM)
Powered-off VM
1
Processor License
Answer
Host A 2 sockets, 4 cores per CPU, 48GB RAM
Host B 2 sockets, 12 cores per CPU, 64GB RAM
64GB 64GB 64GB 64GB
Each vSphere Enterprise Edition license
entitles to 64GB of vRAM. Each vSphere 5 processor license
includes a vRAM entitlement
Edition vRam per License
Enterprise Plus 96GB
Enterprise 64GB
Standard 32GB
Essentials Plus 32GB
(192GB max)
Essentials 32GB
(192GB max)
25
What is the vRAM pool?
Host A
1 1
vSphere Ent
1 1
vSphere Ent
CPU CPU CPU CPU
Host B
VM (4GB vRAM)
Powered-off VM
1
Processor License
Host A 2 sockets, 4 cores per CPU, 48GB RAM
Host B 2 sockets, 12 cores per CPU, 64GB RAM
VMware vCenter Server
Answer
Example
When managing vSphere hosts with
vCenter, vRAM entitlements are pooled
vRAM pool capacity is the max capacity
that can be used with the current set of
licenses
License the following servers with vSphere
Enterprise Edition:
Summary
CPUs 4
vSphere Licenses 4
Pooled vRAM (GB) 256
4 licenses of vSphere Enterprise Edition
provide a vRAM pool of 256GB (4 * 64 GB)
64GB 64GB 64GB 64GB vRAM Pool (256GB)
26
How Many VMs Can I Run with My vRAM pool?
Host A
1 1
vSphere Ent
1 1
vSphere Ent
CPU CPU CPU CPU
Host B
VM (4GB vRAM)
Powered-off VM
1
Processor License
Host A 2 sockets, 4 cores per CPU, 48GB RAM
Host B 2 sockets, 12 cores per CPU, 64GB RAM
VMware vCenter Server
Answer
Example
You can run as many VMs as you want as
long as the consumed vRAM capacity is
equal or less than the vRAM pool
Only powered on VMs consume vRAM
capacity
Summary
CPUs 4
vSphere Licenses 4
Pooled vRAM (GB) 256
Consumed vRAM (GB) 96
User creates 32 VMs with 4GB of
configured vRAM and powers on only 24
24 powered on VMs each with 4GB of configured
vRAM consume a total of 96GB
Powered off VMs do not consume vRAM capacity
27
How Many VMs Can I Power-on a Host?
Host A
1 1
vSphere Ent
1 1
vSphere Ent
CPU CPU CPU CPU
Host B
VM (4GB vRAM)
Powered-off VM
1
Processor License
Host A 2 sockets, 4 cores per CPU, 48GB RAM
Host B 2 sockets, 12 cores per CPU, 64GB RAM
VMware vCenter Server
Answer
Example
You can power on as many VMs as you as
you want on a host as long as the total
consumed vRAM is less or equal to
available vRAM pool
If necessary, you can increase the available
vRAM pool capacity by adding more proc.
licenses to a CPU
Summary
A B Pool
vSphere Lic. 2 2 4
VMs 4 36 40
Consumed vRAM (GB) 16 144 160
vRam Pool (GB) 128 128 256
User deploys 40 VMs each with 4GB of
configured vRAM distributing 4 VMs on Host
A and 36 on Host B
By running 36VMs on host B the user consumes
a total of 144GB on Host B
The two Enterprise Ed. Licenses used for Host B
contributes a total of 128GB of vRAM to the pool
…
28
What if My VMs Move to a Different Host with vMotion or DRS?
Host A
1 1
vSphere Ent
1 1
vSphere Ent
CPU CPU CPU CPU
Host B
VM (4GB vRAM)
Powered-off VM
1
Processor License
Host A 2 sockets, 4 cores per CPU, 48GB RAM
Host B 2 sockets, 12 cores per CPU, 64GB RAM
VMware vCenter Server
Answer
Example
Any VM can run on any host within a vRAM
pool. Since vRAM is pooled across all hosts of
the same vSphere edition under a vCenter
Server, the movement of VMs cannot cause
more vRAM to be needed.
Summary
CPUs 4
vSphere Licenses 4
Pooled vRAM (GB) 256
Consumed vRam (GB) 128
VMs on one host can vMotion to another without
impacting the consumed or available vRAM
capacity.
All VMs can even run on a single host, in effect
borrowing the vRAM capacity of the other host.
29
What is My vRAM Pool if I Have Multiple vCenter Servers?
Host A
1 1
vSphere Ent
1 1
vSphere Ent
CPU CPU CPU CPU
Host B
VM (4GB vRAM)
Powered-off VM
1
Processor License
Host A 2 sockets, 4 cores per CPU, 48GB RAM
Host B 2 sockets, 12 cores per CPU, 64GB RAM
VMware vCenter Server
Answer
Example
The vRAM pool can extend across multiple
linked vCenter Servers. vCenter Servers
(Standard Edition) can be linked together using
Linked Mode.
Site 1 and Site 2 each contain a host with two
licenses of Enterprise. Each site has 128GB of
pooled vRAM capacity in a separate pool.
When the vCenter Servers at each site are linked
together, one vRAM pool is created with 256 GB
of pooled vRAM capacity.
VMware vCenter Server
Site 1 Site 2
Summary
Site 1 Site 2
CPUs 2 2
vSphere Licenses 2 2
Pooled vRAM (GB) 128 128
Consumed vRam (GB) 64 64
Summary
Site 1 and 2
CPUs 4
vSphere Licenses 4
Pooled vRAM (GB) 256
Consumed vRam (GB) 128
You must link the vCenter Servers to form a single
vRAM pool. The resulting vRAM capacity is the
sum of the two site’s vRAM capacity.
30
What is My vRAM Pool if I Have More Than One vSphere Edition?
Host A
1 1
vSphere Ent
1 1
vSphere Ent
CPU CPU CPU CPU
Host B
VM (4GB vRAM)
Powered-off VM
1
Processor License
Host A 2 sockets, 4 cores per CPU, 48GB RAM
Host B 2 sockets, 12 cores per CPU, 64GB RAM
VMware vCenter Server
Answer
Example
Each edition of vSphere has a separate vRAM
pool. Adding licenses for one edition will not
add vRAM to other edition’s vRAM pool.
Host X is licensed with two licenses of Enterprise
Plus. There are two separate vRAM pools: one
for Enterprise with 256 GB, another for Enterprise
Plus with 192 GB.
Summary
Ent Ent+
CPUs 4 2
vSphere Licenses 4 2
Pooled vRAM (GB) 256 192
Consumed vRam (GB) 128 96
Host X
1 1
vSphere Ent +
CPU CPU
31
I Need More vRAM Capacity. How Do I Expand my vRAM Pool?
Host A
1 1
vSphere Ent
1 1
vSphere Ent
CPU CPU CPU CPU
Host B
VM (4GB vRAM)
Powered-off VM
1
Processor License
Host A 2 sockets, 4 cores per CPU, 48GB RAM
Host B 2 sockets, 12 cores per CPU, 64GB RAM
VMware vCenter Server
Answer
Example
There are two ways you can expand your
vRAM pool:
1) Upgrade all licenses to an edition with a
higher vRAM entitlement
2) Add more licenses of the current edition
Summary
CPUs 4
vSphere Licenses 4
Pooled vRAM (GB) 256
Consumed vRam (GB) 256
All 256GB of vRAM capacity is consumed.
Another 16 GB is needed for 4 additional VMs.
… …
32
Summary
CPUs 4
vSphere Licenses 4
Pooled vRAM (GB) 256
Consumed vRam (GB) 256
Example
I Need More vRAM Capacity. How Do I Expand my vRAM Pool?
Host A
1 1
vSphere Ent
1 1
vSphere Ent
CPU CPU CPU CPU
Host B
VM (4GB vRAM)
Powered-off VM
1
Processor License
Host A 2 sockets, 4 cores per CPU, 48GB RAM
Host B 2 sockets, 12 cores per CPU, 64GB RAM
VMware vCenter Server
Answer
There are two ways you can expand your
vRAM pool:
1) Upgrade all licenses to an edition with a
higher vRAM entitlement
2) Add more licenses of the current edition
vSphere Ent + vSphere Ent +
Summary
CPUs 4
vSphere Licenses 4
Pooled vRAM (GB) 384
Consumed vRam (GB) 272
All 256GB of vRAM capacity is consumed.
Another 16 GB is needed for 4 additional VMs.
Upgrading all 4 licenses to Enterprise Plus would
raise the Pooled vRAM capacity to 384GB.
Enterprise Plus is entitled to 96GB of vRAM.
4 licenses * 96GB = 384GB vRAM
… …
33
Summary
CPUs 4
vSphere Licenses 4
Pooled vRAM (GB) 256
Consumed vRam (GB) 256
Example
All 256GB of vRAM capacity is consumed.
Another 16 GB is needed for 4 additional VMs.
Adding one additional license of Enterprise would
increase the pooled vRAM capacity to 320GB.
I Need More vRAM Capacity. How Do I Expand my vRAM Pool?
Host A
1 1
vSphere Ent
1 1
vSphere Ent
CPU CPU CPU CPU
Host B
VM (4GB vRAM)
Powered-off VM
1
Processor License
Host A 2 sockets, 4 cores per CPU, 48GB RAM
Host B 2 sockets, 12 cores per CPU, 64GB RAM
VMware vCenter Server
Answer
There are two ways you can expand your
vRAM pool:
1) Upgrade all licenses to an edition with a
higher vRAM entitlement
2) Add more licenses of the current edition
1
Summary
CPUs 4
vSphere Licenses 5
Pooled vRAM (GB) 320
Consumed vRam (GB) 272
One additional license of Enterprise will increase
the vRAM pool by 64GB, yielding a total pooled
vRAM capacity of 320GB.
… …
34
How Do I License a New Host and Join It to My vRAM Pool?
Host A
1 1
vSphere Ent
1 1
vSphere Ent
CPU CPU CPU CPU
Host B
VM (4GB vRAM)
Powered-off VM
1
Processor License
Host A 2 sockets, 4 cores per CPU, 48GB RAM
Host B 2 sockets, 12 cores per CPU, 64GB RAM
VMware vCenter Server
Answer
Example
A new host, Host C, needs to be licensed.
Host C
CPU
There are two ways to add a host:
1) Add additional licenses of the same edition.
2) If you have more licenses than CPUs, you
can deploy those licenses to the new host.
Pooled vRAM capacity will remain
unchanged.
Summary
CPUs 4
vSphere Licenses 5
Pooled vRAM (GB) 320
Consumed vRam (GB) 144
1
35
Summary
CPUs 4
vSphere Licenses 5
Pooled vRAM (GB) 320
Consumed vRam (GB) 144
vSphere Ent
How Do I License a New Host and Join It to My vRAM Pool?
Host A
1 1
vSphere Ent
1 1
vSphere Ent
CPU CPU CPU CPU
Host B
VM (4GB vRAM)
Powered-off VM
1
Processor License
Host A 2 sockets, 4 cores per CPU, 48GB RAM
Host B 2 sockets, 12 cores per CPU, 64GB RAM
VMware vCenter Server
Answer
Example
A new host, Host C, needs to be licensed.
One additional license of Enterprise is added. This
increases the pooled vRAM capacity to 384GB.
Host C
CPU
There are two ways to add a host:
1) Add additional licenses of the same edition
2) If you have more licenses than CPUs, you can
deploy those licenses to the new host. Pooled
vRAM capacity will remain unchanged.
1 1
VMware vCenter Server
Summary
CPUs 5
vSphere Licenses 6
Pooled vRAM (GB) 384
Consumed vRam (GB) 144
Pooled vRAM capacity is increased
by 64GB. As before, VMs can run
on any of the three hosts.
36
Summary
CPUs 4
vSphere Licenses 5
Pooled vRAM (GB) 320
Consumed vRam (GB) 144
How Do I License a New Host and Join It to My vRAM Pool?
Host A
1 1
vSphere Ent
1 1
vSphere Ent
CPU CPU CPU CPU
Host B
VM (4GB vRAM)
Powered-off VM
1
Processor License
Host A 2 sockets, 4 cores per CPU, 48GB RAM
Host B 2 sockets, 12 cores per CPU, 64GB RAM
VMware vCenter Server
Answer
Example
Host C
CPU
There are two ways to add a host:
1) Add additional licenses of the same edition.
2) If you have more licenses than CPUs,
you can deploy those licenses to the
new host. Pooled vRAM capacity will
remain unchanged.
1
A new host, Host C, needs to be licensed.
No additional vRAM is needed and there are more licenses
than CPUs. A license can be redeployed to Host C. Pooled
vRAM capacity remains unchanged.
vSphere Ent
VMware vCenter Server
Summary
CPUs 5
vSphere Licenses 5
Pooled vRAM (GB) 320
Consumed vRam (GB) 144
Pooled vRAM capacity remains
unchanged at 320GB. As before, the
VMs can run on any of the three hosts.
37
Thank You!