All right, so to finish out with Cluster‑Aware Updating GUI here,
you saw back in Visual Studio Code that we can add CauClusterRole
in order to do the self‑updating configuration, but of course, we
can always do that graphically as well.
But this one can automate the process for you of creating that role.
It says here in the last paragraph on the Getting Started page of
the Configure Self‑Updating Options Wizard that if the CAU
clustered role is not already configured,
the wizard begins by helping you configure the role.
So, as you can see, the options are to enable,
disable, or remove the clustered role.
And then we've just got a graphical surface here for doing our options, our
advanced options, what plugin do you want to use, do you want to use
recommended updates or other products besides Windows,
that kind of stuff? Generate report.
So it's just pretty straightforward. Again,
this is all about delivering Microsoft updates through
either WSUS or the Microsoft update website.
Lastly, I want to make sure we've got at least one
user clustered role on this machine.
So, like I promised you, we're going to do a little bit
more with Storage Spaces Direct here.
I'm going to take the default Cluster Pool here that we looked at
a moment ago, and if we look at Virtual Disks, we can see that
depending upon the kind of storage that's been enlisted and the
number of disks involved,
there's going to be a certain level of resiliency that's put in here. Storage
Spaces Direct also supports tiered storage where you may have some storage
that's solid state and some that's mechanical.
I'm actually running out of compliance with Microsoft in
my lab because all I have are mechanical SAS disks, I
don't have any solid state disks.
So that is the default Cluster Virtual Disk that was created, again,
through that single command, Enable‑ClusterStorageSpacesDirect, it
really does a lot of heavy lifting. But I'm going to right‑click here,
the Pool, and do New Virtual Disk. This asks us first, all right, what
pool are you talking about?
Well,
we only have one. Let me click Next, and I'm going to call this
vm‑csv‑disk, and I'm going to do 80 for the size, and then we'll
click Create. You can see that begin to populate down below in
the virtual disk list.
Now the virtual disk is akin to a partition.
We now have to create a volume,
which is laying down a file system, and that kind of stuff.
I'm going to select my Cluster, my Disk, let's click Next.
I'm going to use all of that 80 gigs.
I'm not going to assign a drive letter here, I'm going to use, ReFS, or the
Resilient File System's the only option, and I'm going to call this
vm‑csv‑volume. Next, and Create. The volume is what we need to actually
store data on, and I'm going to put a highly‑available virtual machine on
it, and at this point it's fuzzy, isn't it?
When you think about, whoa, well, where exactly is that storage?
Well, is it coming from one node or another node?
Well,
we don't really need to worry about that due to that abstraction that's going on under the hood.