Okay, so now I want to look at my resource allocation tab,
and I can see that if I've got this cluster selected,
it shows me my total capacity of memory, my total capacity for our CPU and memory,
how much I've gotten reserved for CPU and memory
So some good good staff to keep an eye on
removing hosts from a cluster or rebooting one.
So my total capacity for the cluster, then for processor
or 11.3 gigahertz, 2.8 gigahertz for the capacity
reserved and then 8.5 for the available capacity.
If we can look in our virtual machines tab,
we can see at a relative basis how much memory and
processor is being consumed by each of the virtual machine.
***, too, is a virtual host,
so it it consumes a fair amount of memory on the real host as well as a lot of its CPU.
the center server appliance in this case,
is the most active VM fires memory requirements.
So we've got some nice stats to look at here
and what we can do is, um,
look at the summary of each of'em individually. If we want to get more detail
on what it's resource usage actually is.
with a virtual host added as a cluster, we get pretty decent performance.
We can look at the performance tab for the cluster itself
and see how the aggregate resource is. Our are doing
the next task that we have to,
uh, have a look at them
would be how to look at the H A slot size.
Okay, so let's look at our cluster
more right click and go to at its settings.
We already have the name picked and we've
turned on a J. So let's go to the age a section
We've got our checkbox for host monitoring, which uses that heart heartbeat data store, the NFS datastore.
We can see now that the reboot of the host has completed, it's finally finished.
So our mission control
we have the two either enable or disable this.
So this tries to set aside he
a reservation of custard capacity
to do fail overs of the virtual machines. So when one host goes down,
should be able to have the capacity to
absorbed wth e v ems, that air moving over to it
so we'll make sure this is selected.
The number of host failures that the cluster can tolerate is exactly one. We've only got a two note cluster.
If we had a three note cluster than we could change this to to
so we can't tolerate to know it's potentially failing.
In this case, with a simple cluster of just two, we can only tolerate a failure of one of those hosts,
so we want to make sure that was changed. We'll go ahead and click, okay,
we'll go back to our summary tab,
and the link we want to click now is the advanced runtime info for the cluster,
various parameters, such as our slot size.
this lot sizes 32 megahertz,
73 megabytes of memory, one virtual CPO. That's that's what it's defined as right now. And the size of a slot effectively determines how many virtual machines you can run on the cluster,
although unless you've got it very finely tuned, one slot does not necessarily equal one of'em,
so it's here. We've got 138 slots total.
Five are being used, 12 are available.
And then we have 100 21 as fail Owers.
Well, go ahead and close that.
Now we're gonna change the CPU reservation for
the wind seven clone.
Now, I want to be able to, uh,
move this this virtual machine back to the host E. It was original living. I can see it's still here
100 doesn't have any running. PM's
all right. So I want to just change the host,
move it back to 0.200
validation succeed session and any problems moving it back,
I'll make it a high priority
and we click finish,
so this should run fairly quickly.
I'll go back to 0.200
and we should see that that virtual machine pop up here in just a moment.
Of'em still running.
Okay, so I'm getting a message saying that this
running long mode guests.
Once in a while, you see a message like this. This one
is just particular to my configuration.
So what I'm going to do is power the VM down
move, move the virtual machine once it's powered off. And I shouldn't have any problems
and your production environment,
you would need to, uh,
Makesem make some adjustments. Make sure you've got actual virtual host. Sometimes there are
problems and you try to simulate a lab with virtual host. So keep that in mind,
but we'll come back in just a moment when all this has been moved over.
It's gonna take a couple minutes.
Okay, so when seven clone to is now
I'll go ahead and close that counsel
Should go very quickly and easily.
All right, that was pretty fast.
Now select that host double check. VM is there.
I can go ahead and power that one back on.
And now what I want to do is
so I could make it larger. I could make it smaller,
and that effects the way that the cluster will perform depending on how many V EMS
are up and running at any given time.
All right, so let's adjust the CPI reservation
for the wind. Seven clone
will right click go to at its settings.
Then we'll go to the resource is tab.
And so you can see we have no Reese Reese reservation set for see pure memory. Both are set to zero megahertz, zero megabytes.
So we're gonna make a reservation for
Sorry for CPU to 512 megahertz.
Well, go ahead and accept that change.
Now I can see that the VM gets reconfigured,
but also we get some changes to the cluster itself.
I go back to the cluster in the inventory and select
I could see that My, my my information has changed.
Now I've got 512 megahertz as a slot size because I've made that a reservation for the CPU.
We've talked about what with the reservations. D'oh!
My mind and memory was 80
was 81 megabytes per slot,
But whereas before I had 115 slots. Now I am only 22
so I've made the slots Maur.
I've given each lot more Resource is
so therefore they have less slots available.
I've only got 16 for fail over and only one available
with these particular parameters.
So this just goes to show that you can adjust the slots
to make them larger or
and then actually enforce
a particular slot size
So if I go to my cluster
now, I want to go to edit settings for the cluster.
I'll go back to V. Sphere A. J,
in order to put in a advanced option,
I need to click the Advanced Options button
and you double click in that little window there. Then you can type in
something more specific.
If the option we're going to use as daz dot slot
we're gonna pick 300 megahertz.
Now we're not gonna go into a whole lot of detail about
all the different available advanced options. That's a topic for another, another video.
trust me for now, to know that this particular option
megahertz of the CPU allocation will be per slot.
So we'll go ahead and click. Okay,
Now let's inspect the advance runtime info to link one more time.
Now I can see the slot size went from 5 12 done a 300
memory state roughly the same,
but Now I have 37 slots in my cluster.
Whereas before I had 22
I still got five or six years, depending how many Of'em were running.
And now, now that I've lowered
the CPU requirement for your slot, I can actually say I've got four in reserve
27 available for fail over.
So by adjusting this up and down, we can see how
to reallocate the total aggregate resource is available in the given cluster.
Okay, so our last task
undo some of these settings.
So first thing we're going to do is get rid of that requirement we just added
about at its settings for the Cluster
Select Free Spirit chain.
Go back to advanced options
and I can just select this and delete it.
Select this and delete it.
I also want to undo my CPU reservation for the Window seven clone.
So I go back to edit settings here,
to my resource is tab
I'm just gonna replace 5 12 with the default which is zero.
And for kicks, we can go back to the cluster
and look at the advanced runtime info link one last time
see how that changed.
So now I gotta back up. 218 slots for cluster
noticed the slop size by default is basically 1/10 of what we had sat itude previously.
It went from 300 megahertz 2 32 megahertz. Which means I've got ninth lots of with this configuration available
in 104 for fail over.