2 hours 58 minutes
you're watching Model fire. Peaceful advanced features Bison three v Sphere, Distributed Resource Scheduler or DRS.
By the end of this video, you'll understand what DRS does and how to configure it.
Fees for DRS is another cluster future office fear
it balances resource consumption across posts by migrating v EMS from overwork hosts to less overworked ones.
Do your issues is demotion to achieve this.
So in order to use DRS, you'll need to satisfy all the requirements for the emotion.
So the arrest is actually an automated be emotion and has three automation levels
manual where you run DRS manually and choose if you want to migrate some PM's or not
partially automated where DRS makes migration suggestions to you, but it doesn't apply them until you approve them
and fully automated, where DRS works everything on itself behind the scenes and present you with the balanced data center Pretty cool.
In addition to balancing computing load across hosts, DRS can also let you define affinity rules or anti affinity rules for V EMS and hosts. What do I mean by that? Well, suppose you have to virtual machines that should not run on the same years ex I host.
You can define an anti affinity rule between those two PM's in such a way that when DRS attempts to migrate one of them,
it takes into consideration the empty affinity you configured and put sitting a different host.
If the trivia mes are already on the same post, then DRS will detect that and will migrate one of thumb toe another host.
On the other hand, if you want to vm to run on a specific host
and not on any other host, you can define an affinity rule between the V M and the hosting question, and you're s will also take that into consideration.
Years does a lot more interesting things, but for the sake of simplicity, we can't cover them all. That's now jumping to the center and configure DRS.
Now all rpm's are running on the same host. Remember, we shut down his ex? I too, in the previous lesson and V's fear h a restarted thumb on host one. Now yes, X, I want is running all the V EMS and yes, excite, too, is running. None seems like an unbalanced data center here.
But before enable and testy rs,
we need to make sure the VM czar only shared data store
because DRS. And thus the emotion required the PM's to be only shared data store. The work Virtual Machine is on the local data store, so let's migrated to a shared one using story of emotion.
Uh, let's do the same with the email VM.
The two database via MES are already on a shared data store. We did that in the previous lesson.
Now all virtual machines are only shared data store. Before we actually enabled the RS, let us cause a CPU contention in the first years Excite House by stressing the CP use off some virtual machines running on it.
Because a CPU spike there is a neat utility in Lenox called stress. It lets you strain the CPU and cause it to use all the available computing resources it has. This way we are going to create a clear unbalance in the CPI your consumption between the two hosts.
So let's do that.
Opening counsel to the Web VM
and typing the Command Express Dash C one. The one here represents the number of CPU course you want to stress.
let's do the same with the email be in.
It will take some time to settle at 100% of CPO consumption. You can monitor CPU usage on both house and you can see here that yes, X I won is using almost all the computing capacity off its CPU.
While yes, excited, too, is sitting idle. Since no VM is running one,
this is most inconvenient.
We need to fix that by enabling DRS on the cluster.
So right, click the cluster and choose settings.
Then click on these few DRS
and you can see it is turned off. That's turn it on. Click on the edit button,
then click on the toggle button next to restrict the arrest to enable it
leave the automation level to the default. It's on fully automated
and also leave the migration threshold or the aggressiveness level toe default and hit. OK,
now, if you click on the cluster in the inventory and then go to the summary,
you can see in the middle pain that there is a tab showing the level of balance in the data center.
If you refresh the screen, it should show as imbalanced because he is excited. One is using way more CPU than he is. Excited, too.
Dearest will detect this imbalance and will select one or more vehemence to migrate to host to in order to balance the load.
So refresh the page and monitor what is about to happen in the recent tusks.
It could take a dozen seconds to a minute,
and lo and behold, there it is migrating the Web BM that is causing the trouble to the second years. Excite us.
Let's wait for the migration to finish,
and when it's done, you can see that the Web Veum is now running on. Yes, excite, too.
And if you check the CPU usage for both hosts, you'll see that things look better now
by migrating the Web PM, DRS. Relieved the first host from some load.
You can also monitor the cluster balance by clicking on the cluster,
then on monitor on on CPU utilization. Under these fear, DRS.
You can see that Host One is using slightly more CPU than Hearst, too.
But it is way better than before.
It is difficult to find the perfect balance when you only have two hosts, but things are already looking way better. Thanks to these were DRS.
That was a quick demonstration of what piece for the arrest does.
Thanks for watching. And I'll see you in the next video.