Lesson 3 Part 1 - Resource Pools
Video Activity
Resource Pools This lesson covers resource pools and discusses the following: Describing resource allocation for CPU and RAM Setting resource pool parameters Describing expandable reservations A resource pool is a logical way to extract CPU and memory and allows for a prioritization of resources going to a virtual machine (VM) or a collection of VM...
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 »
Video Description
Resource Pools This lesson covers resource pools and discusses the following:
-
Describing resource allocation for CPU and RAM
-
Setting resource pool parameters
-
Describing expandable reservations
A resource pool is a logical way to extract CPU and memory and allows for a prioritization of resources going to a virtual machine (VM) or a collection of VMs.
Video Transcription
00:09
Hello. I'm Dean Campiglio. Welcome to the Cyberia Virtual ization course
00:13
we're now working when in module 10. We're going to do Lesson three where we talk about resource pools.
00:20
So resource pools will describe how this works for our CPU and memory. Resource is
00:26
well, look at the different parameters that you can adjust for a resource pool and we'll talk about the expendable. Sorry, rather expandable reservation.
00:36
So a resource pool is a way to logically abstract are CPU and memory.
00:42
What I can do for a standalone host or a cluster, perhaps using DRS distributed resource Scheduler
00:48
great resource pools.
00:50
And
00:52
when you do this allows you to
00:54
prioritized the resource is that go to a V, M or collection of the EMS,
01:00
and you could also have virtual machines
01:03
within a resource pool and child pools.
01:07
So, for instance,
01:08
when I have the host selected,
01:11
this becomes my route resource pool. All the resource is that I have available route of those resources is within the host itself,
01:19
and I can create a resource pool. We get this little icon looks like a pie chart.
01:23
I've got one here for production with two V EMS
01:26
inside that resource pool in another one for test with two of'em,
01:32
I could also
01:34
have a child pool.
01:37
I can call this one development
01:40
and have
01:42
another V m here,
01:45
and you can see by the nesting that this is a child pool of this.
01:49
And these two are child pools of this.
01:51
So it gives you that hierarchy to organize how the resource is air divided up,
01:57
and for each of the resource pools that are defined thes three anyway, I have the ability to organize them anyway. I wish so that is very flexible.
02:07
I can isolate certain V EMS, for instance.
02:09
You're testing development. Virtual machines most likely don't need very much. Resource is developers, and people doing testing aren't expecting to get the very high performance. Let's say,
02:22
but your production v. EMs. On the other hand, you want to give them a CZ. Much resource is as you can within reason, balancing with your other requirements, of course,
02:30
but these two of'em are the ones that are running the organization's business or the application, so we want to give them the most memory and processor that we can based on what's available.
02:42
It can also define permissions
02:45
on the resource pool objects in the inventory, so that provides another level of access control
02:51
and effectively. What I'm doing is abstracting the available resource is in my host and subdividing them among different groups of the EMS.
03:00
So it's a great organizational tool
03:01
and allows you to spread the resources around as you see fit.
03:06
So some of the attributes that we would expect for a resource pool are just like what we talked about earlier, with limits, reservations and shares for memory and processor. I can still define shares, reservations and limits
03:19
for each resource pool separately,
03:21
but I also have the option to use an expandable reservation.
03:24
This is an interesting idea where if I have the expanding reservation check box
03:30
set to yes or if it's checked, it's basically said to Yes.
03:35
Now the EMS that air in this pool of'em there, this pool and this pool can all draw from the parent pool.
03:43
So this means that I can expand what production requires once in a while, much like the balloon driver borrows memory from other V EMS and
03:52
puts it where it's needed. Expandable reservation works very similarly thes be EMS might need more resources
03:58
so they can borrow more from the parent pool and thereby reducing the amount available to the test and death pools.
04:05
If reservation is not expandable, that's set to know
04:10
now. VI EMS within this pool could only draw from the from the parent pool. So of'em is three and four Need or let's say of'em three needs more more resources than it currently has. It can only borrow from what the test resource pool was allocated. To begin with. It can't borrow from the root.
04:28
That's only when the expandable reservation option is used.
04:31
So if we think about a scenario,
04:34
I've got two departments in the organization. Engineering and Finance Engineering is providing 1/3 of the budget. Finance provides 2/3 of the budget,
04:46
and each of these groups has their own test and development virtual machines.
04:49
So if I look at my host, my route resource pool is 12,000 megahertz of CPU and four gigs of Ram.
04:58
So just we're looking at the CPU here for engineering.
05:00
I've got engineering test and engineering production engineering pool itself
05:06
the parent pool. Anyway, I've allocated 1000
05:11
megahertz of CPU with the reservation of 1000.
05:15
So I'm saying I need a minimum of 1000. That's actually my same amount that I've allocated.
05:18
But I've also said that the limit could be 4000
05:24
for for the pool and its expandable.
05:27
So for the test
05:28
sub pool of engineering, I can allocate another 1000 no reservation required in a limited 4000 and then subdividing it again. I can say that the production pool is going to get 2/3 of the available,
05:44
uh,
05:45
resource is for this pool with a reservation of 2 50 a limited 4000 again
05:49
so you can see between production and test. I can break this down and more finely tuned. The resource is that each of those pools gets.
06:00
If we think about it with the Finance Department, 2/3 of the available would go to finance 1/3 to engineering. So that's roughly 2000 and 1000 shares each of the available
06:13
12,000 That's that's here,
06:15
or another way you could think of it is finance could have as much as 8000 megahertz. Engineering could have as much as four thousands. That would be your 2/3 of 1/3 split
06:25
but I want to keep someone reserved for other uses, so I don't have to
06:29
as long as I have the ratio. Correct. It doesn't matter how how many shares are youse. Then from within the engineering pool, I can define my test and production pools, giving them their appropriate levels of CPU. Resource is,
06:45
and within the finance parent pool, I can have sub pools for finance test systems, 1000 megahertz and finance production systems get 2000 megahertz.
06:57
So as we can see you can you can really break this down. You could even have 1/3 level if you want, or fourth or fifth level. But really, having a parent pool with a sub pool is probably enough flexibility for most situations.
07:09
So to recap,
07:11
we talked about what a resource pool is, how it lets you subdivide.
07:15
The available resource is that your host provides so all the physical memory, all of the physical processor power can then be split up and divided among the different groups that you define.
07:26
And we know that we can
07:28
count on the parent pool here and some sub pools of the parent and even a sub pool of a sub pool, so it's a sub sub pool.
07:38
We know that this give you great ability to organize how the resource is are allocated among Gurvey EMS and thinking about it in the production versus test and development context really helps Thio decide how you want to allocate. You're remembering your processor.
07:54
We also talked about a scenario where I've got two different groups within the organization
07:59
and I could give 2/3 of the resource is to one group and 1/3 to another and then subdivide that further with some testing development pools.
08:07
So that concludes the lesson three. Thank you.
Up Next
Similar Content
