server virtualization -...
Post on 21-Sep-2020
34 Views
Preview:
TRANSCRIPT
Server Virtualization
Antony Parzakonis
Server Virtualization
What is it and how does it work?
Previous licensing model
Updated model (Server/CAL)• External Connectors
• Device CALs
Management Servers
Per-Processor Servers• Hyperthreading and multi-core technology
• SQL Server 2005 Enterprise Edition (EE)
Windows Servers• W2003 R2 EE
• W2003 Datacenter
SQL Server (Server/CAL Model)
Vista Enterprise Centralized Desktop (VECD)
Multiplexing
What is it and how does it work?
VM technology -> multiple O/S’s on a single physical
server
Before this could only run one O/S at a time
VS 2005 R2 adds a layer on top of the original O/S
VM works by allocating virtualized resources to VM’s
Hypervisor technology will eliminate need for VM
software
Improved chip designs better enable VM technology
What is it and how does it work?
Physical Hardware System
(“Server”)
Operating System (“OS”)
Virtual Machine (“VM”)
Technology
OS OS
Application Application
Physical
OS
Environment
Virtual
OS
Environments
Virtual HW
System
Virtual HW
System
Allocates
virtual
resources
Virtual· processors· RAM· network card· etc.
Physical· processors· RAM· network card· etc.
Physical and virtual hardware and OS environments
What is it and how does it work?
Physical and virtual OS environments
Application Application
Physical Hardware System
(“Server”)
Operating System (“OS”)
Physical OS Environment
Physical Hardware System
(“Server”)
Operating System (“OS”)
Virtual Machine (“VM”)
Technology
OS OS
Application Application
Physical
OS
Environment
Virtual
OS
Environment
Virtual
OS
Environment
Physical Hardware System
(“Server”)
OS OS
Application ApplicationPrimary
Virtual
OS
Environment
hypervisor
Virtual
OS
Environment
A Before VM technology B VM technology (non-hypervisor)
such as Microsoft Virtual Server 2005 R2
C Virtualization Services in the OS
(hypervisor technology)
Previous licensing model
PUR rules for physical servers (not proc.) also applied
to VM tech
• Each instance or installation required a license!
Needed a separate OS and application license for each
VHD (virtual hard drive) file
Whether the software was running or not
Previous licensing model
Server with multiple stored VHD files
.VHD
SAN storage
· 6 .VHD files on
server’s hard disk
or on a SAN
· Each contains an
instance of
Windows Server
and Exchange
Physical Hardware System
(“Server”)
WS WS
Exchange Exchange
Hard disk storageB
A
Instances of software
running on a server.VHD .VHD
.VHD .VHD .VHD
.VHD .VHD .VHD
.VHD .VHD .VHD
Updated Model
Products are licensed by running instance
Each license grants right to run a certain number of
instances at any one time on the licensed server
Create and store any number of instances, doesn’t
matter where they’re created or stored
No longer talk about an “installed and used” number
Right to run one instance at a time per assigned
license
Makes it easier to move instances
Can also reassign licenses but not on a short term
basis >90 days (unless retiring the hardware)
No separation of components (unless permitted)
Updated Model
Running an instance of Exchange Server in a physical
or virtual OS environment
Server (“A”)
Windows Server
Exchange
A Run 1 instance of Exchange in
a physical OS environment
MICROSOFT
CORPORATION
Exchange
Server (“A”)
Windows Server
Virtual Server
WS
Exchange
B Run 1 instance of Exchange in
a virtual OS environment
Virtual
OS
Environment
OR
Physical
OS
Environment
Updated Model
Applying the updated licensing to a centralized library
scenario
.VHD
SAN storage
· 6 .VHD files on
server’s hard disk
or on a SAN
· Each contains an
instance of
Windows Server
and Exchange
Physical Hardware System
(“Server”)
WS WS
Exchange Exchange
Hard disk storageB
A
MICROSOFT
CORPORATION
2 Exchange
MICROSOFT
CORPORATION
2 WS
Instances of software
running on a server.VHD .VHD
.VHD .VHD .VHD
.VHD .VHD .VHD
.VHD .VHD .VHD
Updated Model
Moving instances of software from one server to
another
Instance of
Windows Server
Instance of
Exchange
Microsoft
Microsoft
Microsoft
Microsoft
Microsoft
Microsoft
Microsoft
Microsoft
SAN: 4 logical drives,
each containing an
instance of Windows
Server and Exchange
Server (“A”)
Windows Server
Exchange
Server (“B”)
Windows Server
Exchange
MICROSOFT
CORPORATION
Exchange
MICROSOFT
CORPORATION
WS
MICROSOFT
CORPORATION
Exchange
MICROSOFT
CORPORATION
WS
Updated Model
Move instances of software from one rack-mounted
server to another
Storage
· 6 .VHD files on
server’s hard disk
or on a SAN
· Each contains an
instance of
Windows Server
and Exchange
MICROSOFT
CORPORATION
Exchange
MICROSOFT
CORPORATION
WS
MICROSOFT
CORPORATION
Exchange
MICROSOFT
CORPORATION
WS
.VHD .VHD .VHD .VHD .VHD .VHD
Server A Server B Server C
Updated Model
Reassigning a software license from one server to
another
· 6 .VHD files on
server’s hard disk
or on a SAN
· Each contains an
instance of
Windows Server
and Exchange
.VHD .VHD .VHD .VHD .VHD .VHD
Storage
MICROSOFT
CORPORATION
Exchange
MICROSOFT
CORPORATION
WS
Server A Server C
Not within 90 days
of last assignment/
reassignment
Updated Model
Software may not be separated to run in more than one
OS environment under a single license
Virtual
OS
Environment
Exchange
SQL
Windows Server
OR OR
OR
Physical
OS
Environment
Virtual
OS
Environment
Windows Server
Physical
OS
Environment
SQL Server Exchange
Server (“A”) Server (“A”)
MICROSOFT
CORPORATION
SBS
Premium
MICROSOFT
CORPORATION
3 SBS
Premium
A 1 license for SBS Premium –
Software must run in one OS environmentB 3 licenses for SBS Premium –
Software can run in three different OS
environments
External Connectors
PUR states that an EC required for each copy of the
server software being accessed
WS WS WS
. . .Access
Access
Access
Access
External User
Access
MICROSOFT
CORPORATION
WS
. . .
MICROSOFT
CORPORATION
WS EC
MICROSOFT
CORPORATION
WS EC
MICROSOFT
CORPORATION
WS EC
MICROSOFT
CORPORATION
WS EC
Server “A”
External Connectors
Updated Model licenses per Server
Now an EC allows you to access any number of
instances running on the server
WS WS WS
. . .Access
Access
Access
Access
External User
Access
MICROSOFT
CORPORATION
WS
. . .
Server “A”
MICROSOFT
CORPORATION
WS EC
Device CALs
Device CALs licensed per device, not per O/S
environment on that device
• But multiplexing rules still apply!
. . .Access
Access
Access
Access
Device “A”
MICROSOFT
CORPORATION
WS CAL
`
MICROSOFT
CORPORATION
WS
Server “B”
Management Servers
Management licenses licensed per managed device,
not per managed OS environment
• But multiplexing rules still apply!
. . .Manage
Manage
Manage
Manage
MICROSOFT
CORPORATION
WS
Server “B”MICROSOFT
CORPORATION
MOM
MICROSOFT
CORPORATION
MOM OML
Server “A”
Per-Processor Servers
Previous licensing for Per Processor products was by
physical processor
Server
“A”Proc Proc Proc Proc
Virtual
OS
Environments
Physical
OS
Environment
Virt.
Proc
WS
BTS
MICROSOFT
CORPORATION
4 WS
MICROSOFT
CORPORATION
4 SQL
MICROSOFT
CORPORATION
4 BTS
BTS
Virt.
Proc
WS
BTSBTS
Virt.
Proc
WS
SQLSQL
Virt.
Proc
WS
SQLSQL
Per-Processor Servers
Updated model licensing Per Processor products is
now by virtual processor
• The number of licenses required to run instances on a physical
processor not running VM tech has not changed
Server
“A”Proc Proc Proc Proc
Virtual
OS
Environments
Physical
OS
Environment
Virt.
Proc
WS
BTS
MICROSOFT
CORPORATION
4 WS
MICROSOFT
CORPORATION
2 SQL
MICROSOFT
CORPORATION
2 BTS
BTS
Virt.
Proc
WS
BTSBTS
Virt.
Proc
WS
SQLSQL
Virt.
Proc
WS
SQLSQL
Per-Processor Servers
You can also assign more virtual processors than
actual physical processors
Server
“A”Proc Proc
Virt.
Proc
Virt.
Proc
Proc Proc
WS
SQLVirtual
OS
Environments
Physical
OS
Environment
WS
SQL
Virt.
Proc
WS
SQL
Virt.
Proc
WS
SQL
MICROSOFT
CORPORATION
6 WS
MICROSOFT
CORPORATION
5 SQL
MICROSOFT
CORPORATION
1 BTS
Virt.
Proc
WS
SQL
Virt.
Proc
WS
BTS
Hyperthreading/Multi-cores
Virtual processors are considered to have the same
number of threads and cores as each physical
processor in the underlying hardware system
Server
“A”
Proc 1
Core Core
Virtual
OS
Environments
Physical
OS
Environment
· If a physical proc has
two cores, for licensing
purposes, a virtual proc
also has two cores, even
if the cores are allocated
from separate physical
processors
Proc 2
Core Core
Virt. Proc
Core Core
WS
SQL
Virt. Proc
Core Core
WS
BTS
MICROSOFT
CORPORATION
1 SQL
MICROSOFT
CORPORATION
1 BTS
MICROSOFT
CORPORATION
2 WS
Hyperthreading/Multi-cores
Virtual OS environments that use only fractions of a
virtual processor still count as a full processor
Server
“A”
Proc 1
Core Core
Virtual
OS
Environments
Physical
OS
Environment
· If a physical proc has
two cores, for licensing
purposes, a virtual proc
also has two cores
· If you choose to allocate
only one core to a
virtual proc, it still
counts as a full virtual
proc
Proc 2
Core Core
Virt. Proc
Core
WS
SQL
Virt. Proc
Core
WS
BTS
MICROSOFT
CORPORATION
1 SQL
MICROSOFT
CORPORATION
1 BTS
MICROSOFT
CORPORATION
2 WS
SQL Server 2005 EE
To be announced in July and made retrospective for
existing customers
If all physical processors are licensed for SQL Server
you are permitted to run an unlimited number of virtual
processors as well
Windows Servers
Windows Server 2003 R2 Enterprise Edition lets you
run up to five instances on a server
• You can substitute Windows Standard for Enterprise
Server “A”
Windows Server 2003 R2
Enterprise Edition
Virtual Server
WS 2003
R2 EE
WS 2003
R2 SE
WS 2003
R2 EE
WS 2003
R2 SE
MICROSOFT
CORPORATION
1 WS 2003
R2 EE
Virtual
OS
Environments
Physical
OS
Environment
1
Windows Servers
Windows 2003 R2 Datacenter (per proc. licensing)
After the appropriate number of licenses are acquired
and assigned, you may run;
• One instance of the server software in the physical OS
environment, and
• Any number of instances of the server software in virtual OS
environments
CALs are still required to access the server
Server “A”
Windows Server 2003 R2
Datacenter Edition
Virtual Server
WS 2003
R2 SE
WS 2003
R2 EE
WS 2003
R2 EE
WS 2003
R2 DCE
MICROSOFT
CORPORATION
1 WS 2003
R2 DCE
Virtual
OS
Environments
Physical
OS
Environment
MICROSOFT
CORPORATION
1
SQL Server
For SQL Server 2000 Workgroup Edition and SQL
Server 2000 Standard Edition, you need a license for
each instance of SQL Server running in an OS
environment
• You also need separate licenses for each OS environment in which
you run the software
• Only one SQL Server 2000 Enterprise Edition license is required to
run the two instances of SQL Server 2000 Enterprise Edition in the
virtual OS environment
Server “A”
Windows Server 2003 R2 Enterprise Edition
Virtual Server
WS 2003 R2 EE
SQL EE SQL EE
MICROSOFT
CORPORATION
1 WS 2003
R2 EE
Virtual
OS
Environments
Physical
OS
Environment
MICROSOFT
CORPORATION
2 SQL 2000
SE
MICROSOFT
CORPORATION
1 SQL 2000
EE
WS 2003 R2 EE
SQL SE SQL SE
SQL Server
For SQL Server 2005 Workgroup Edition and SQL
Server 2005 Standard Edition, while you still need
separate licenses for each OS environment in which
you run the software, a single license permits you to
run any number of instances in a single OS
environment
Server “A”
Windows Server 2003 R2 Enterprise Edition
Virtual Server
WS 2003 R2 EE
SQL EE SQL EE
MICROSOFT
CORPORATION
1 WS 2003
R2 EE
Virtual
OS
Environments
Physical
OS
Environment
MICROSOFT
CORPORATION
1 SQL 2005
SE
MICROSOFT
CORPORATION
MICROSOFT
CORPORATION
1 SQL 2005
EE
WS 2003 R2 EE
SQL SE SQL SE
Microsoft Corporation- NDA Material
Vista Enterprise Centralised Desktop
• Current approaches to desktop deployment;
• Virtual PC’s
• Diskless PC’s and Remote Boot
• NEW Centralised Desktop for PC’s and Thin Clients
• Provides secure storage of VM’s on a server to either
PC’s or thin clients
• Advantages; security and reduced hardware footprint
• Ideal customer; banks and security organisations
• Needs strong IT experience
• New SA benefit
• Annual subscription (in addition to SA); $40-64 USD for
diskless PC’s
• $117 USD for Thin Clients
Vista Enterprise Centralised Desktop
Diskless PCs
User A
User B
IT Pro
SAN
Data CenterB
A
1. Dedicated Hard Drive
Stored on SAN or NAS
2. Remote Boot Off the
Network
Diskless PCs
New SA Benefit Allows Diskless PC
and Remote Booting
VECD Licensing Options
Windows
licensed PC
covered by
Software
Assurance
Thin Client
(incapable of
running
Windows
Client OS)
Data Center
Unlimited number
of virtual machine
environments can
be created and
stored on any
number of internal
network servers
VECD for SA
Subscription
Access up to
4 running
instances per
subscription
license
VECD
Subscription
Access up to
4 running
instances per
subscription
license1
2
31 2 3
Microsoft Corporation- NDA Material
Licensing Model & Eligibility
• Licensing Model• Use rights permit the following:
• Right to create and store unlimited dormant virtual machine instances on a remote network device
• Right to remotely access and run up to 4 virtual machine instances running on up to 4 network servers
• Eligibility• Available to all VL customers in EA and Select VL Programs
• Customers that deploy this solution with rich client PCs must have these PCs covered with Software Assurance for Windows
• Customers can deploy this solution with thin client devices using the thin client SKU (priced at parity for devices that do not have a Windows license or Software Assurance coverage)
Multiplexing
• Multiplexing or pooling hardware and/or software does
not reduce the number of CALs required
Multiplexing. Users / devices that access a SQL server indirectly require a CAL
Multiplexing
Except when...
.
Multiplexing. Manual transfers of reports, that subsequently don’t access a SQL
Server don’t require CALs
Thank You
top related