Windows Server 2012 Virtualization: Notes from the Field

2,239 views

Published on

More info on http://techdays.be.

0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
2,239
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
66
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Windows Server 2012 Virtualization: Notes from the Field

  1. 1. Windows Server 2012 Virtualization:Notes from the FieldDidier Van Hoye, Architecthttp://workinghardinit.wordpress.comKurt Roggen, Technical Consultanthttp://trycatch.be/blogs/roggenk
  2. 2. Agenda • WS 2012 Hyper-V & Failover Clustering • VM Priorities • Maintenance Mode • Failover & Failback • Anti Affinity • Live Migration • Cluster Aware Updating (CAU) • SC 2012 SP1 Virtual Machine Manager • Cluster Management - Availability Sets • Fabric Patching • Maintenance Mode • Service Templates
  3. 3. Hyper-V &Failover Clustering
  4. 4. WS 2012 Failover ClusteringOptimize & automate placement logicVirtual Machine Priority Enhanced Failover PlacementStarting the most important VMs first Each VM placed based on node with bestEnsure the most important VMs are available memory resources running Memory requirements evaluated on a per  Preemption to shut down low priority VM basis VMs to free up resources for higher  Non-Uniform Memory Access (NUMA) priority VMs to start awareIdeal for infrastructure servers (DCs) or tiered architecture (back- end, middle-tier, customer-facing) High Medium Low
  5. 5. Priorities for Roles or Virtual Machine Values: High, Medium, Low  Default Priority: Medium High  Lowest Priority: No Auto Start Starting Roles in Priority order Medium  Per Node Placing Roles/VMs in Priority order  Cold start Low  Handling node crash Moving Roles/VMs in Priority order No Auto Start  Queuing  Node Drain
  6. 6. Virtual Machine Priorities Default Priority: Medium Default “Move Behavior”: Quick migration for Low & below Defined by cluster parameter “MoveTypeThreshold” which defaults to 2000 (Medium or Higher Priority)
  7. 7. VM Priorities & Live Migration Set all VMs to Live Migrate (instead of Quick Migrate)  Not only VM with Medium/High Priorities VM Priority Values  3000 = High  2000 = Medium  1000 = Low  0 = Do not start automatically Using PowerShell  Get-ClusterResourceType "Virtual Machine" | Set-ClusterParameter MoveTypeThreshold 1000
  8. 8. Enhanced Failover Placement • Enhanced memory aware placement of VMs • Check for most available Memory • Failover is determined by Preferred Owners & Possible Owners • Failback of VM now uses Live Migration instead of Quick Migration • Live Migration respects Preferred Owners & Possible Owners • Default Failback action: No Failback
  9. 9. Anti Affinity ClassNames • Property of ClusterResourceGroup • Identify ClusterGroups that should not be hosted on the same node (where possible) • Impacts VM Placement and Live Migrations • Configurable using PowerShell only • Configurable using SC2012 SP1 VMM using “Availibility Sets” • Serves as basis for “Availibility Sets” in SC2012 SP1 VMM More information: http://msdn.microsoft.com/en-us/library/aa369651(v=vs.85).aspx
  10. 10. Cluster Node Maintenance Mode Drain all VMs off a node Supports all cluster roles Role-specific features  Live migration or quick migration for VMs  Uses VM Priority  Moves other roles
  11. 11. Cluster Node Maintenance ModeWorkflow – In Depth Cluster Node Maintenance Mode - Automated Node Drain Node is PAUSED Workload sorted based on Priority VMs queued for live migration (using MaxLiveMigrations) Enhanced memory aware placement of VMs Cluster Placement Policies (Preferred & Possible Owners, AntiAffinity) VMs’ live migrated concurrently along with built-in retry logic Automated Node Drain completed
  12. 12. Cluster Aware Updating(CAU)
  13. 13. Cluster Aware Updating (CAU) Update orchestration across all nodes in a cluster  CAU ships in box with Windows Server 2012  Not reinventing Windows Updates & patching  Previews, applies and reports on updates for a cluster Two modes: Self-updating & Remote-updating  Self-updating: Workload reduction through increased automation, Updating itself is resilient  Remote-updating scenarios where closer administrator attention is preferred or warranted Extensible  Integrate with your patching tools with plug-ins (API)  Two inbox plug-ins: Windows Update & hotfix plug-in  Per-node pre-update and post-update scripts
  14. 14. Where Does CAU Fit In? Windows Update Services
  15. 15. Plug-ins & Supported Update TypesCAU ships with two plug-ins 1. Windows Update 1. Installs GDRs* => From Windows Update Or WSUS 2. Hotfix Plug-in 1. Installs QFEs** from a SMB 3.0 file share 2. 3rd party updates such as BIOS & Firmware Updates from a SMB 3.0 File Share
  16. 16. Cluster Aware Updating Process Windows1. Scans, downloads and installs applicable Jenny Starts Update, WSUS, QFE, Updating Run updates on each node …  Windows Update or Hotfix plugin or both CAU2. Restarts node as necessary Pause Node & Resume Node &3. One node at a time Drain VMs ... Failback VMs4. Repeats for all cluster nodes5. Customize pre- & post-update behavior Node 1 with PS scripts .6. Easy manual or scheduled launch Windows . Server failover  Via GUI cluster .  PowerShell Node 64  Works for both physical or virtualized clusters
  17. 17. Remote-Updating Mode CAU Update Coordinator process Node 1 Node 2 remotely connects to the cluster User-initiated Updating CAU Update Run, allowing real time monitoring Coordinator Failover Cluster Rich progress updates Minimal Server Core (no .Net or Node 3 Node 4 PS dependency) on nodes
  18. 18. Self-Updating Mode Leverages a CAU cluster role that is Update Coordinator resilient to planned and unplanned failures Node 4 Node 1 Requires no real-time user attention Failover Cluster Installs updates on a custom schedule CAU Update Coordinator process runs on a clustered node Node 2 Node 3
  19. 19. Hotfix Config FileHotfixes Folder Extension Rules <MSU> <MSI>Structure & Security <MSP> Folder Rules Strict ACL Checking (Optional) <MySwUpdateType> Kerberos Mutual Authentication CAU Hotfix Root Folder (Required) CAUHotfix_All Hotfixes applicable to all nodes Data integrity checking (Required) MySwUpdateType  SMB Signing or SMB Encryption Special software updates <Node Name 1> Hotfixes applicable just to <Node Name 1> Privacy with SMB Encryption . MySwUpdateType (Optional) . Special software updates .  SMB Encryption is new in Windows Server 2012 <Node Name N> Hotfixes applicable just to <Node Name N> MySwUpdateType Special software updates
  20. 20. “Hotfix” Support Internals Rich/extensible Hotfix installation  Microsoft QFEs, or third-party driver updates, or even Firmware/BIOS updates… Select hotfix behavior at start. Two key inputs: 1. Root Folder: on an SMB File Share 2. Configuration xml file: defines the Rules System32WindowsPowerShellv1.0ModulesClusterAwareUpdatingDefaultHotfixConfig.xml Configuration Rules are the key to flexibility  Easy to specify new Rules  hotfix installer name, install options, reboot behavior, return values etc.
  21. 21. NTFS permissions CAU File Share First you‟ll need to do your home work as described in the TechNet article But that doesn‟t quite cover it Adjust NTFS Permissions on the CAU Share  Give cluster node computer accounts (or an AD group containing them, which makes for easier administration) Read/Execute permission to the location  If Not =>they can‟t run the DUPs.
  22. 22. NTFS permissions Log File DUPs allows logging with /L switch Locally (per node) or to central share Must use another share than the CAU Share:  Need to give the computer accounts (or an AD group containing them, which makes for easier administration) write permission to the location  You‟re not allowed to do that for other then specific accounts as described on TechNet The log can grow quite large if used a lot  Keep an eye on it  For clarities sake use different log per cluster or folder type
  23. 23. CAU Hotfix plug-in in action
  24. 24. Cluster ManagementUsing SCVMM 2012 SP1
  25. 25. VMM 2012 SP1: Cluster Management • Supports “Possible/Preferred Owner” • Supports of “Availability Sets” (Anti-Affinity) • Supports VM Priority • Supports CSV2 • Supports 64 cluster nodes, 4000 VM‟s/cluster, 1024 VMs/node
  26. 26. Possible Owners & Preferred Owners
  27. 27. VM Priority
  28. 28. VMM 2012 SP1 support forAnti-Affinity = VMM „Availability Sets‟ Availability Set = configurable anti-affinity rules for VMs Ensures VMs are placed on different hosts for better availability VMM Placement algorithm offers suggestions based on availability sets Works across:  Standalone (non-clustered) Hyper-V hosts*  Hyper-V clusters*  Xen Server hosts  VMware hosts
  29. 29. Availability Sets
  30. 30. Availability Sets & VMM Services VMM Services can leverage „Availability Sets‟  Availability sets – configured at the machine tier level  Ensures that VM instances of a machine tier are placed on different hosts. SSUs can request availability sets for their VMs  Simple checkbox experience  Available from the VMM Service Template Designer
  31. 31. Fabric PatchingUsing SCVMM 2012 SP1
  32. 32. Update ManagementFeature of VMM 2012Keeps Windows Fabric Servers up-to-date• Limited to VMM managed infrastructure servers (HV, LIB, WSUS, WDS)Enable Manage Scan Remediate ManageFeature Baselines Servers Servers Exemptions
  33. 33. Remediating Hyper-V Cluster Orchestrated workflow  Put a node in maintenance mode  Evacuates the node using Live Migration  User can override this to save state the VMs on the node  Install missing updates based on baselines assigned  Take the node out of maintenance mode  Go to next node and repeat Supports WS2008, WS2008 R2, WS2012 Hyper-V clusters Automatable using PowerShell
  34. 34. VMM Services &Service Templates
  35. 35. Standardize Application Deploymentusing Service Templates Service template (Multi-tier applications) Web tier Application tier Data tier Scale out & health policy Scale out & health policy Scale out & health policy IIS Web (IIS) Application(Server App-V) Custom Scripts App server Data (SQL) SQL Web Deploy DAC Packs HW profile OS profile App profile HW profile OS profile App profile HW profile OS profile App profile Compute Storage Network
  36. 36. Create Service Template withService Designer Use the ribbon for contextual actions within the Service Template Designer. Use the designer canvas to build your service template from Virtual Machine Templates, Logical Networks and Load Balancers. Set service-related properties such as cost center, description, release version.
  37. 37. Deploy Service ThroughDeployment Preview Preview pane shows view of your service deployment. Settings allow you to set deployment specific variables. Ribbon bar for deploy activity or to check deployment ratings.
  38. 38. Why Use Services? Standardized deployments (in dynamic way – multiple environments) Manage multi-tier applications across multiple servers as a single unit Scale out based on demand Composibility of OS and Applications, allows users to manage fewer OS images Automation using # GCEs (Generic Command Execution ~ scripts)
  39. 39. Generic Command Execution (GCE)Execute custom scripts within Service instance VMs  Can specify run as account, script restart behavior, logging properties  Script parameters can leverage configurable service settingsMultiple entry points available  Application level  Pre/post install, pre/post uninstall, pre/post service, save/restore state  Application Profile level  Pre/post install, Pre/post uninstall  Pre/post install supports multiple, ordered scripts (SP1)
  40. 40. SC 2012 SP1 VMM: Services Service Deployment  Support for Service deployment to untrusted domains and workgroups  Support for Service deployment to disconnected VMs Application Host  “Web Application Host” for deploying MS Web Deploy packages to existing web servers (virtual, physical, farm, clustered) SQL Server 2012  Complete installation of prepared SQL 2012 instances Linux Guest support  Supporting Linux Operating Systems for unattended deployment
  41. 41. In-VM/Guest Agent SP1 Changes Requires .NET 4.0  Agent installation will take care of this (can sysprep as well)  For Server Core, requires Windows Server 2008 R2 SP1 or above Deployed via ISO  All service instance VMs have a guest agent installed Decoupled from VMM server  Supports Service deployment to untrusted domains and workgroups  Supports Service deployment to disconnected VMs
  42. 42. Service Template Explorer An add-in for your VMM Console, that allows you to discover, download and import pre-configured service templates directly to your VMM infrastructure Service Templates available (soon)  Windows Server 2008 R2 SP1 / Windows Server 2012  ADDS Domain Controller  DNS, DHCP  Web Server (IIS)  File Server* THIS IS BETA AT THE MOMENT AND MIGHT CHANGE TILL RTM
  43. 43. Service Template Explorer Experience

×