Bringing the cloud to youWhat if you could have the control of the datacenter
and the power of the cloud?
Reduced developer chaos and shadow IT
Simplified, abstracted experience
Added consistency to modern development
One portal, one user experience
Write once, deploy anywhere
Q1 CY2008
Windows Server 2008Released
Q3 CY2009
Windows Server 2008 R2Released
Q3 CY2012
Windows Server 2012Released
Q3 CY2014
CURRENT
Change
Since Hyper-V Released
Control plan
Data plan
Datacenter Abstraction Layer
Physical hardware
Compute cluster
Virtual machines
Storage cluster
File servers
Security controller
Shielded VMs
Windows Server | Hyper-V | System Center
Network controller
Virtual networks
Provisioning and operations
World class scale, performance, and availability
Best-in-class support for Linux
Frictionless “cloud-cadence” infrastructure upgrades
High-performance Live migration and Storage QoS
Guest clustering
Mission-critical scale: SQL, Exchange, SharePoint, SAP, Oracle
Broad distro support, including: RHEL, SLES, Ubuntu, CentOS
Hot add | remove vNIC and
in-guest vRSS
Rolling upgrades without downtime, no new hardware needed
Mixed-mode clusters
Cloud-scale fundamentals
SDN infrastructure Hybrid datacenter extension
Network function virtualization
Data plane based on Azure
High-throughput, low-latency packet processing [up to 40G]
Programmable network controller based on Azure
NVGRE, VXLAN, and OVSDB support
Load balancer that is proven in Azure
Distributed firewall
Custom service chaining, including Linux appliances
Azure ExpressRoute
Multi-tenant gateways
Cloud-scale, cost-effective platform
Scalable hybrid-cloud storage solution
Workload-aware protection
Cross-site availability and disaster recovery
Storage Spaces Direct
Predictable workload performance with Storage QoS
Microsoft StorSimple
Azure storage
Azure Site Recovery
Azure Backup
Sync replication with Storage Replica
• “Stretch” clusters with automatic failover
• Cluster-to-cluster replication with orchestrated recovery
Control and monitor administrator privileges
Detect and respond to breach faster
Protect virtual machines from compromised host
Add access and usage policies to sensitive information
File Classification Infrastructure
Azure Rights Management Services
Dynamic Access Control
Just-in-time administration
Just enough administration
Next generation credentials
Hardware-rooted security
Shielded virtual machines
Guardian Service
Improved Security Event Logging
Cloud-based security analysis
Out-of-the-box anti-malware
Host Guardian Service
Spotlight capabilities
Shielded Virtual Machines can only run in fabrics that are designated as owners of that virtual machine
Shielded Virtual Machines will need to be encrypted (by BitLocker or other means) in order to ensure that only the designated owners can run this virtual machine
You can convert a running Generation 2 virtual machine into a Shielded Virtual Machine
•
•
Set-VMFirmware "Ubuntu" -SecureBootTemplateMicrosoftUEFICertificateAuthority
•
•
•
•
Set-VMReplication "VMName" -ReplicatedDisks(Get-VMHardDiskDrive "VMName")
•
•
•
•
•
•
•
•
•
Add-VMNetworkAdapter -VMName “TestVM" -SwitchName "Virtual Switch" -Name "Fred" -Passthru |
Set-VMNetworkAdapter -DeviceNaming on
Get-NetAdapterAdvancedProperty | ?{$_.DisplayName -eq "Hyper-V Network Adapter Name"} | select Name, DisplayValue
•
•
•
•
http://blogs.msdn.com/b/powershell/archive/2008/06/05/credssp-for-second-hop-remoting-part-i-domain-account.aspx
•
•
•
•
•
Start with a Windows Server 2012 R2 cluster All nodes running Windows Server 2012 R2
The workload supports Cluster OS Rolling Upgrade process
Cluster OS Rolling Upgrade Process
Windows Server 2012 R2
Cluster Functional Level = Windows Server 2012 R2
Windows Server 2012 R2
Windows Server 2012 R2
Windows Server 2012 R2
Windows Server 2012 R2
Failover Cluster
Migrate Workloads Off Cluster Node Pause | Drain the node
Cluster OS Rolling Upgrade Process
Windows Server 2012 R2
Cluster Functional Level = Windows Server 2012 R2
Windows Server 2012 R2
Windows Server 2012 R2
Windows Server 2012 R2
Windows Server 2012 R2
Failover Cluster
Evict Idle Cluster Node
Cluster OS Rolling Upgrade Process
Windows Server 2012 R2
Cluster Functional Level = Windows Server 2012 R2
Windows Server 2012 R2
Windows Server 2012 R2
Windows Server 2012 R2
Windows Server 2012 R2
Failover Cluster
Re-Provision Node Install New OS
Install and Configure any Workload Requirements
Cluster OS Rolling Upgrade Process
Windows Server 2012 R2
Cluster Functional Level = Windows Server 2012 R2
Windows Server 2012 R2
Windows Server 2012 R2
Windows Server 2012 R2
Windows Server 2016
Failover Cluster
Re-Add Node To Cluster Using Cluster UI or PowerShell
Cluster Functional Level Remains Windows Server 2012 R2
Cluster OS Rolling Upgrade Process
Windows Server 2012 R2
Cluster Functional Level = Windows Server 2012 R2
Windows Server 2012 R2
Windows Server 2012 R2
Windows Server 2012 R2
Windows Server 2016
Failover Cluster
Ready To Migrate Workloads Back Migrate workloads to Windows Server 2016 Node
Validate functionality
Cluster OS Rolling Upgrade Process
Windows Server 2012 R2
Cluster Functional Level = Windows Server 2012 R2
Windows Server 2012 R2
Windows Server 2012 R2
Windows Server 2012 R2
Windows Server 2016
Failover Cluster
Repeat For Remaining Nodes
Cluster OS Rolling Upgrade Process
Cluster Functional Level = Windows Server 2012 R2
Windows Server 2016
Windows Server 2016
Windows Server 2016
Windows Server 2016
Failover Cluster
Windows Server 2012 R2
Windows Server 2016
Windows Server 2016
Windows Server 2016
Windows Server 2016
Windows Server 2016
Upgrade Functional Level Cluster Functional Level upgraded To Windows Server 2016:
Update-ClusterFunctionalLevel cmdlet
New functionality added in Windows Server 2016 enabled
No longer possible to add a Windows Server 2012 R2 node to the cluster
Cluster OS Rolling Upgrade Process
Windows Server 2016
Cluster Functional Level = Windows Server 2016
Windows Server 2016
Windows Server 2016
Windows Server 2016
Windows Server 2016
Failover Cluster
Upgrade is completed
Cluster OS Rolling Upgrade Process
Windows Server 2016
Cluster Functional Level = Windows Server 2016
Windows Server 2016
Windows Server 2016
Windows Server 2016
Windows Server 2016
Failover Cluster
•
•
•
•
•
Update-VMConfigurationVersion
•
•
•
•
•
•
•
••
•
•