Lab 21 Part 2 - Distributed Resource Functionality Scheduler for a Cluster of Hosts (cont.)

Video Activity

Exploring the Distributed Resource Functionality Scheduler for a cluster of hosts (Lab—Continued) This lab-based lesson continues the lesson on Distributed Resource Functionality Scheduler. In this lesson, participants learn how to create a rule to tell DRS that that a particular VM should always run or must not run on a particular host. Participan...

Join over 3 million cybersecurity professionals advancing their career
Sign up with
Required fields are marked with an *
or

Already have an account? Sign In »

Difficulty
Intermediate
Video Description

Exploring the Distributed Resource Functionality Scheduler for a cluster of hosts (Lab—Continued) This lab-based lesson continues the lesson on Distributed Resource Functionality Scheduler. In this lesson, participants learn how to create a rule to tell DRS that that a particular VM should always run or must not run on a particular host. Participants learn how to use the cluster function to add a rule.

Video Transcription
00:04
Okay. Now the migration has been completed so we can verify
00:08
that
00:09
when seven Clone one is now running on 10.100
00:14
and when seven is now running on 200.
00:18
So let's do a little bit of clean up here. We're gonna go back to our settings,
00:23
natural rules, and we can get rid of this rule. We no longer need it.
00:28
Well, go ahead and click. Yes.
00:32
Now we want to create a rule
00:34
that would
00:35
tell de arrest that a particular VM should always run
00:39
or must run
00:41
or should not run or must not run. You have those different choices
00:46
eso
00:47
on a particular host. So I can say, for instance,
00:51
that I want Win seven Clone one
00:54
to always run on host 200.
00:58
So I'm still in my rules area of the cluster settings. I'll click add when add a new rule
01:04
and we'll call this rule
01:07
when Sudden
01:10
Clone one
01:11
on host 200.
01:15
It's good to be descriptive with your rule names so that you know what you've created when you go back later and look at this
01:23
for this rule type
01:23
virtual machines to host is what we want to pick
01:27
and you'll notice that the de arrest lets you pick or let you designate groups.
01:33
I don't have any V EMS in a group. I don't have any hosting a group yet, so we'll go to
01:38
this tab DRS. Group's manager
01:42
first, I'll create a group of virtual machines.
01:47
Quickly add button
01:49
and we'll call this group
01:51
when. Seven. Clone one.
01:53
We're only putting one virtual machine in this group. We're just doing a very simple demonstration here,
02:00
but obviously you could make much more complex setups. As I mentioned earlier, you could group together
02:07
virtual machines of a certain
02:08
performance characteristics like Web servers or
02:13
database servers or email servers. That kind of thing. We're just gonna pick one V. M. It's now in. The group will click okay,
02:20
and similarly with the hosts,
02:23
this is under the host TRS groups.
02:24
We're gonna call this
02:28
group host 200.
02:30
That's the only host we want in the group.
02:32
So we'll click. Okay there,
02:36
like OK, again.
02:38
Now my rules created.
02:40
So when seven clone on host 200 I'll click. Okay.
02:46
And if I run the arrest, I should get a recommendation.
02:50
That tells me that win seven clone.
02:52
One
02:53
should be moved from 0.100 dot 200 to satisfy the host affinity.
03:00
Really,
03:01
so I can go ahead and click,
03:04
apply recommendations.
03:07
Get that process started
03:10
and this will take a little while to run.
03:14
But it's fairly quick.
03:20
Okay, so that's completed.
03:22
Now we can see
03:23
that the Wind clone or Win seven Clone one is no longer running on host 100
03:29
and is now in fat running back on host 200 proving that the
03:34
the V EMS to host rule works as we expect.
03:38
So let's go in and do a little bit of clean up as we did before.
03:44
Go ahead and remove that rule,
03:47
and I can go ahead and remove these groups because I no longer require them.
03:53
Okay, so that concludes
03:57
Lab 21. So we've seen how
04:00
DRS works
04:01
with fail overs and with affinity and anti affinity rules as well as
04:08
rules, too.
04:09
Buying V EMS to particular hosts
04:13
in next lab will be working with
04:15
the update manager,
04:18
so we'll install that
04:20
and see how the cluster settings need to be modified
04:25
will create a patch baseline.
04:28
We'll attach the baseline, look for updates and then stage the patches to be installed or or remediated
04:35
on our hosts.
04:38
Thanks. And I'll see you in the next lab.
Up Next
Patch Management Part 1 - Introduction to the Module
Patch Management Part 2
Patch Management Part 3
Lab 22 Part 1 - vSphere Update Manager (lab) - Update the VIC
Lab 22 Part 2 - vSphere update manager (lab 2) Configuration