When creating the Nano Server VHD files, I installed the Hyper-V role by selecting the –Compute parameter. As we have already created the cluster and the virtual disk, we could simply go ahead and create VMs now.
Before doing that, I wanted to configure the Hyper-V Servers to store VM configurations and VHD files on the Cluster Shared Volume and I created a virtual Switch that can be used by the VMs:
As you can see, I’m using the $cimSessions variable from part 1 again. This variable contains CIM Sessions to my four Nano Servers, so that the above lines do configure all servers at once. Here’s how I’ve created those sessions:
$cimSessions = New-CimSession -ComputerName n01,n02,n03,n04
Now we are ready to create the VMs and add them to the cluster. I copied the “win2012r2.vhdx” file over to the ClusterStorage and used this as a parent disk for my VMs:
That was pretty easy, so lets have a look at what our current environment looks like in the Failover Cluster Manager.
We see all the VMs that were added to the cluster and we can go ahead and move them around between nodes using the Failover Cluster Manager. The same goes for the “nodes”, we see all four Nano Servers participating in the cluster and we can control the nodes status:
In the storage folder of the FCM we see the virtual disk and some information about health status and capacity:
Ok, that is pretty basic stuff if you just look at the Hyper-V part. The interesting point however, is that those same servers do also provide the shared storage that the hypervisors use.
Stay tuned for more
This post has been migrated from our earlier blog based on BlogEngine.NET.