Windows Server 2012: Part 5.3—Clustering and Hyper-V Awesomeness

Slalom consultant and accomplished Microsoft systems developer Derek Martin sheds light on Windows Server 2012 (WS12) through his insightful blog series focusing on his research within the technical preview documentation, personal experimentation with the product, and thoughts of how they can apply to the real world as soon as it is released to manufacturing (RTM).

Slalom Consultant Derek Martin

Slalom Consultant Derek Martin is an accomplished Microsoft systems developer and integrator, experienced in developing and deploying SharePoint and CRM solutions, integrating line of business applications, and leveraging existing infrastructure investments.

One of the challenges I can already see with all that is new and good when building out my private cloud is which of the following amazing clustering storage ‘things’ should I use to enable my cloud?

  1. SMB Direct
  2. Cluster Shared Volumes
  3. Traditional Block Storage
  4. Shared Nothing

I don’t have an answer yet, but I do know that there are a variety of tools that SMB2 supports (as discussed in a previous post) brings to the table. Additional items are outlined here.

Within a single cluster, I can now have 4,000 virtual machines (VMs). Excessive? Depends on how many nodes you have or how big those nodes are. Regardless, that’s a lot of VMs! The nice thing is that I can now perform large amounts of tasks across my VMs collectively (bulk migrations, updates, etc.) and Clustering Services is smart enough to keep things up and running by queuing things up when the load gets high, powering off lower priority VMs (called preemption), etc.

Non uniform memory access (NUMA) aware virtual machine placement. NUMA is important to understand and something I am still working on.  Essentially, it is a way for Hyper-V VMs to be aware when NUMA is in use on a Host and allows the VM (and placement engines) to evaluate more fully whether a VM will run successfully on a host. Cool underpinning.

Automatically draining a cluster node. If you consider my previous blog on Cluster Aware Patching, this makes sense. When you put a host node into maintenance mode to patch it, be smart—move the VMs off to other nodes and then patch.  Then, perform the next host node, etc. This also extends to the VMs themselves which is a bit freaky.

These are all underpinning things, but speak to the power of what the clustering services will be able to do for me. Next time, I’m going to return to my storage question and talk more about Cluster Shared Volumes and what Windows Server 2012 did to them.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: