Oh, I'm doing fine. Paleo. Welcome to Cyberia. We're talking about the virtual ization installation configuration management course, and we're now in module 12 hosts scalability.
So in this lesson will be describing the different functions of a deer esque cluster.
What E. V C means it's enhanced the motion compatibility. We'll talk about some of the benefits that that provides.
See what's involved with creating a de arrest cluster. We'll look at the deer s cluster info
and remove the host from DRS. Closer so you can see how that works.
This lesson will be in several parts,
so stay tuned for the other parts after this one.
All right, So what is the cluster? We've talked about this a little bit previously. It's a collection of hosts and v EMS.
In this case, we have high availability and disaster. Sorry. Distributed resource scheduler enabled A chain DRS cluster is what we're looking at.
Do you arrest gives us a lot of advantages. When we power up of'em,
we get a recommendation for its initial placement within the cluster. So if I'm gonna power of'em three,
the rest can tell me. Well, it should probably go on the SX two based on the bolo that CSX warning the SX two are using
how much memory and and processor is available would determine where DRS thinks the VM should should go to best take advantage of your available resource is
dear. Us also allows low bouncing.
So if I have to be EMS on, let's have all three of'em zanni SX. One
decide that one of those beams will be best to move to the second host,
so I've got 201 1 on the other. Now the load is banned list a little bit better,
and you can also use DPM, which is distributed power management, and this will actually power down your hosts when they're not needed. So if you had a multi host cluster, let's say like four or six hosts
as your uh, your workload builds up during the day,
you're all of your hosts will be running. But as the workload tapers off, perhaps some of the V EMS could be moved to three hosts, or maybe even two hosts and the other to host could be powered down
when the workload rises up again. Those other hosts could be powered up in V EMS. We move to them.
So this lets you save on the power requirements of keeping all four hosts running at all times. It's a great future.
We don't get to explore that in the lab, unfortunately.
Okay, so what kind of prerequisites do we need for dear s?
First of all, the VM should should all be the motion compatibles. All the requirements for
the motion should be met in north to allow the V EMS to move between the different host When DRS
makes a recommendation to do so.
Also, the most in the cluster have to be part of the V motion Network.
If you want to use load balancing so you might define a network called the Motion and softer VM Colonel Port enable that future which we'll see in the lab.
But that needs to be there so that the thieves to host can communicate with each other to allow the PM's to move back and forth.
Both of the hosts. Russians say both, but all of the hosts in the cluster need to be connected to the same shared storage.
This is because we might be moving the VM files in addition to the VMS than themselves being registered with each host.
All of the discs for the V EMS need to be on that same shared stores, so they're accessible to both hosts.
And then we have to make sure that our show storage capacity is large enough to hold all the V EMS in this case, these three of'em.
So both those canasta up access to storage. The story is large enough to hold all the PM's at once.
Then the registration from one host to another for different VM
can be done with DRS load balancing.
amazing when this all works as expected.
So, one of the things we have to think about is the automation level that we'd like to the arrest Coster to utilize.
You can start with a manual automation level, which means that you manually decide whether the EMS go and manually decide to be motion them around to do your load balancing.
This is a great way to begin using DRS.
Just so that you can have it tell you what the recommendation is. But you don't actually apply the recommendation automatically. You decide to do it manually. So this gives you a chance to see how the software works and become more comfortable with it.
We could make the automation level partially automated, which means that now the placement of initial VM power ups will be automatic.
However, the dynamic balancing still has to be done manually.
On the last option is to fully automate
the automation level. Now, the initial the emplacement and the dynamic balancing has done automatically for you.
You'd only want to go to this level. Once you're sure that your manual load balancing initial placement activities were producing the results you wanted.
You wouldn't want to go to fully automated right away, especially without considering the migration threshold
settings. Because then you might end up with the EMS moving around more often than you wish and causing different kinds of problems because of that.
Speaking about the migration threshold, this is a slider that you can see when you're looking at your automation level, and we can go from conservative all the way too aggressive
at the conservative side.
D. L s uses basically three different
ah priority levels for making recommendations.
If it's conservative than on Lee. Those things that a priority one will be will be used for recommendations to be moved around.
If we're somewhere in the middle than priorities, one into the EMS will be recommended to move for low bouncing or initial placement purposes. And then, if you become aggressive, move it all the way to the right side. Now, priorities 12 and three will be used
for moving VM around and their initial placement. So this gives you the ability to kind of Taylor how aggressive you want the relocation of the EMS to be.
And again, this is something you want to ah,
play around with a little bit before you decide to use in production so you can get an idea of how it works and what the appropriate settings are for your particular environment.
All right. Moving along to E V c
that stands for enhanced of emotion compatibility,
the option to use incompatible CP use on the host within your cluster
up until ah, a couple of recent versions off of S X I This wasn't possible for the center,
but this is a sort of a newer future, but it is really powerful. You have three different options here. We can leave EVC disabled, which is what it is by default,
or you might enable it for a M D hosts or your Intel hosts.
So it's one of these three options that you're allowed to choose here
and effectively. What this means is that if you've got a
ah cluster with Intel hosts that have different CPU families,
you might be able to add 1/3 Intel host of that cluster with a different CPU family altogether if you enable the E V C.
We cannot mix and match Intel a name D host in the cluster unfortunately,
but this is a great feature to give you better compatibility when you want to do the emotion in between hosts.
If the if you don't have even see enabled now you're you might have to do a cold migration, which means the VM must be powered off before it can be moved to another host.
With this enabled, we can leave the VM up and running, and the way that this works
is that the Baseline CPU compatibility
gets determined by the hosts in that cluster. So we enable e V C.
We can force the hosts to look at all their their CPU instruction sets and four features and pick one that becomes the baseline.
So if I I could have three different entire CP use, one of those becomes the baseline because it's the one that has the most in common with the other two.
All of the host in the cluster will now use the baseline CPS features, which means that if you've got a older legacy system and you've got some newer systems that are in the cluster, the legacy says that will end up being the baseline. So you you don't want to use this feature if you don't have to, because
ideally you're hosting. Your clusters should be identical if possible.
Same processor, same amount of memory. This gives you the most predictable performance, and it's easiest to maintain,
uh, where, if your host cannot be configured to use the baseline, let's say it's just so different than the other hosting the custard that it won't be able to join the cluster. So some checking is done
during the, uh, the effort to join a host to a cluster.
So the VC gives us the ability to be a little flexible the way we use that.
So we have several requirements listed here.
Uh, the CPS must be from a single vendor in your cluster
for intel. They have to be court to micro lock a tractor or newer. And for a MD has to be Opteron
first generation or newer.
So keep that in mind when you're
trying to decide which hardware you would like to use.
You must be running at least 3.5, update two or later for your E S X. I host installation,
but the hosts almost be connected to the center
in the BIOS settings for the host, the virtual ization hardware setting must be enabled.
And if you looked at your bios for your host, you've probably noticed it's under. Usually it's under advanced CPU features. So look for that.
And then we have the next X d bit.
This means that we can do, um,
or or for Andy or Intel CP use. And what this means is when we expose this setting to the to the cluster,
this also changes your ability to do the motion compatibility
so we'll talk about that a little bit more in the lab and you'll see what that looks like on the interface
and then, lastly, both of the herd up both. But all of the hosts in your cluster must be configured for the motion. In order for this to work, we want to move the EMS from one host to another.
So we talked about what a cluster is. Some of the features that DUI arrest provides initial placement,
load balancing and power management.
Then we have the prerequisites. The PM's must be the motion compatible. All the hosts on the PM's must be connected to shared storage.
We looked at the different automation levels and your migration threshold, so you'll have to play around a little bit to get comfortable with how they work.
Then we know what the VC bit does and why that's important for
using different CPU families with from the same vendor.
We talked a little bit more about what the cluster requirements were.
Faras, which CPU family's heir compatible Which version of the SX I
being connected to be center and so a lot. All right, stay tuned for the next part. Thank you