Well, there are a variety of features that have been improved in this arena in WS8. At the base of all of these new clustering features is Cluster Aware Updating. Other technologies like Cluster Shared Volume improvements, SMB amazingness improvements and the management tools help ease these burdens, but again, having your Cluster service know what’s happening when you are patching is key. Here’s how it works:
- One of your cluster servers becomes an ‘orchestrator’ – it scans and downloads patches to all of it’s brothers and sisters.
- It then moves VM’s around, maintaining cluster quorum and, by the grace of the Hyper V Resource Metering feature, keeps your SLAs in check by balancing and even powering down less important VMs if resources get pinched – holy cow indeed!
- Once a cluster node is drained, it patches, restarts, rejoins the cluster and the VMs are moved back onto the node and then particpates in helping out other nodes by taking on their VMs as directed from the big brother orchestration node.
Oh yeah – that’s hot. Again, when you pair this stuff with the high availability cluster shared volumes feature and the new transactional SMB goo, you’ve got yourself a self healing/patching private cloud.
Bear in mind – the example here with VMs is just one use case – this totally works with other clustering applications like SQL, Exchange, plain ol highly available file shares, the new highly available DHCP stuff…the sky is the limit!