How are you doing?
And welcome back.
Now in today's video, we'll be discussing about the dynamic skating.
Now, at the height of it, all of you.
There are two primary beach of approaches that are available.
One is the manual skating.
And second is that dynamic skiing.
So many skating is something that we have already seen.
So in today's video, we'll be focusing more on that dynamic skating.
Now, again, one important part to remember is that there are other skating options that are available.
Apart from that, one of the example would be scheduled skating that you can use.
However, today, let's go ahead and focus more.
The dynamics.
Now, when you configured the dynamic skating, you define how to skate the capacity of your auto skating
group in response to changing them mind.
Now, as opposed to the manual scaling, their dynamic skating will automatically modify their desired
capacity of your auto skating group based on the auto demand of the easy two instances pod maybe added
Lord balance element.
So they do discuss our dynamic scaling their three primary skilling policy types.
One is their target tracking scaling.
Second one is the step scaling.
And third one is that simple scaling.
So at a high level or you we should know what each one of these mean.
Now, before we proceed for the let me in fact, show you all of these three.
So within one of the authors getting look, whether desert and minimum is zero, if you go to the auto
scaling here and within these scaling policies, if you add a policy or you're under the policy, thank
you, you'll see that there are three policy types that have a really big target tracking steps, killing
and simply scaling.
So let's go in and understand each one of these at a high level Waterview.
The first one is the simple Skilling policy.
So with the simple Skilling policy, you can configure a specific number of instances to be added.
Then a threshold has reached a certain value.
So this can be better explained with this data.
And very you have a policy type of simple skilling and you have a cloud would allow.
Which basically looks for C.P.U utilization, which is greater than 60.
So now if the oral c.p.u utilization is higher than 60 percent, then you have a big action where you
can go ahead and add certain amount of more easy to instances as part of the auto scaling group.
So this is what simple Skilling policy does.
So let's quickly look into it quickly.
Now within the policy.
Let's quickly select a simple skilling here and this Skilling policy name.
Let's also call it as simple Skilling.
Now, Virginia, you have to select a specific load which allow so currently you see that there are
no alarms that are available.
Let's quickly go ahead and create a cloud.
Which alarm will quickly do a select matrix?
The select matrix would be based on easy to buy auto scaling group.
And we'll be using the Matrix name of Sepehr Utilization Audio.
So currently it assures you what is the average sepehr utilization.
Since there are no instances running, you do not see any updated graph.
So let's go ahead and select this matrix.
So within that video, you can go ahead and select one of the period.
Let's use one minute and you can modify things accordingly within a deconditioned that threshold date.
Let's use static whenever the sea view utilization is greater or greater than equal to Lordi could do
Alduin.
So let's see.
Greater than equal to, let's say, 50 percent.
Let's do a next.
Now you can either also trigger a notification.
Let's remove the notification.
Let's do a next.
And allow me.
Let's say higher than 50.
Let's do a next.
It also shows you this in graph so that it is easier for us to understand.
We will go ahead and do a create alarm.
Great.
So coming back to the Skilling policy, if I quickly refresh, were you you can select the cloud with
Lambert is higher than 50.
Now the question is, what happens if the alarm is initiated?
So it does C view utilization is greater than equal to 50.
And this alarm is initiated.
What should the Skilling policy do?
So that could be as part of AIHRC action, that of ag remove or sector.
So let's see.
And we'll see.
We want to add three more capacity units.
So now you can go ahead and do a grid.
So now what is happiness?
Your skating policy of simple skiing is enable now in order to effect things are working as expected.
Let's quickly do one thing.
Let's have a demo.
So let's say minimum is one, desired is one.
And then Gordon updated so that instance gets created.
So let's quickly open ABC to console.
And as expected, we have one easy two instance that is indeed creating steam.
So let's quickly wait for a moment here.
Great.
So are instances running all too quickly?
A very fater security group.
So currently the security group does not allow a.
So let's quickly also modify the security group.
So what we'll be doing is we'll be generating some load on this easy to instance and then if the scaling
policy is working as expected.
So within the inbound rule, let's quickly add one rule.
So currently, this is my IP address.
And let's add one rule here on board 22.
And we allow IP address to connect.
So once then list quickly connect to the instance.
So I quickly copied the public IP and let's quickly log in.
I switched to the user.
So if you look into the Cebu utilization, the oral load average is very low.
So let's quickly generate a high law based process.
So I'd say PD input would be Babbs zero.
Output would be.
No.
And we turn it off landing.
Now, before we do that, let's also log in to the server from a different domain.
Are there ways since this guy itself will take a amount of C.P.U.
You would not be able to connect to that.
So do it in a lot of banks.
Great.
So let's generate the Lord Aurier.
And from this, he let as expected.
You see that the 99 percent of the CBO is already in the consumption stage.
So after a few moments, if things are working as expected.
Seen both scaling policy will go ahead and launch additional instances.
So in that time, let's go ahead and discuss about that scaling policies.
The second one is the step Skilling policy.
So instead of scaling the adjustment of the current capacity of the instances in your auto skilling
group vary based on the size of the island bridge.
This is very important.
Now, when you discuss about a simple Skilling policy here, that things are very simple.
So if the idea of Sepehr utilization is greater than 60, then add three more capacity units.
So this is a very simple way.
So even if the alarm is 80, the alarm of sleep utilization is 90 or 100.
In all such cases, it will only actory three capacity units as opposed to that step.
Scaling allows much more higher flexibility.
So you're you can state that add one capacity unit when it is 60, then at three more capacity unit.
When the oral c.p.u utilization is greater than 70 and maybe if it is greater than 90, then act fabled
instances.
So at every step of the alarm breach, you can add a specific amount, both instances, or maybe remove
them.
So this is the step Skilling policy.
So let's quickly do one thing.
Let's go to the cloud, watch.
And you see that cloud, which is within this spate of alarm now, within the easy to instance, as
when you see that three more capacity units, basically three more instances are currently upended.
And if so, this is what the simple Skilling looks like.
Now, one important point to remember here is that in simple skilling, you do not really see or you
do not have the flexibility of choosing how many instances should be launched based on the amount of
a love matrix.
So that is what steps Skilling allows us to do.
So let's quickly look in to what Deb Skilling does.
So let's add one more policy audio.
This time we'll be using this step skilling.
So within this step, Skilling, let's quickly choose Declaw Bertalan.
So we didn't you you can say add to capacity unit.
When this utilization is 50.
So now let's add one more step.
So you're let's say 50 to 60.
And from here, if it is more, then you can add three more instances here.
Or maybe you can change this from 60 to 80.
So now if the load is increasing more, then you can go ahead and add more instances, audio in a similar
way.
You can also remove the instances if the amount of load is decreasing at every step.
Great.
So I would make a high level or do you understand the difference between a simple and spend the last
one?
Is there target tracking policy so that their target tracking policy, you select scaling matrix and
set a target value?
Now, this game policy AGS or removes the capacity as required to give the Matrix Act or laws to the
specific target value.
So let's assume that we have a target tracking policy or you're the Matrix Bank is our recipe utilization
and the target value is 50.
So now that target, that policy will always a show and it will always add and remove.
You see two instances to make sure that the average CPI utilization always remains to be 50.
So this can be better understood with the example of Pottermore step.
So basically a thermostat is a component which senses the temperature of a physical system.
And by foam's access so that the system's temperature is maintained, Nereid desired set point.
So, for example, let's say the desired is 24 degrees Celsius and that the room temperature is 18 degrees
Celsius.
So now what would happen is the thermostat will increase that temperature so that the current matches
that of the design.
So this is what thermostat does in a similar way.
Even their target tracking policy box.
So let's take an example.
So let's say that target value is 50 percent.
And there are two easy two instances that apparently available.
So since both of them are having an average of 50 percent, things seems to be fine.
There will be no action that will be performed.
However, at a later stage, there is a little high amount of law and the average CPM utilization is
70 percent across the board, the CPRS.
So now what will happen is since the actual value is more than that of their target value, that target
tracking policy will go ahead and add one more easy to instance automatically so that the order target
value is somewhere close to 50 percent.
Now, at a later stage, let's assume that traffic has decreased.
So now the average C.P.U utilization is fifteen, fifteen, 15 percent across all of these two instances.
So now, again, the actual value is much more lower than that of their target value.
So now that target practice policy will go ahead and remove the ABC next too easy two instances so that
a single easy two instance has a C.P.U utilization of 45 percent, which is close to that.
All right.
I'll get to you.
So let's also quickly see that.
So within the policy, take the stand.
Let's select the target tracking policy.
So this is a very straightforward policy.
You do not really need to first create a cloud which alarm similar to what we had seen in simple.
So all you have to do, select a target tracking policy and the matrix.
Again, there are multiple matrix.
So let's assume Sepehr utilization.
You select a target value, which is 50 and you could and created and that's about it.
Now, before we continue, I just wanted to show you one more important thing.
So currently, as part of this step, scaling in total, we have four easy two instances.
So what happens in Dynamic Skilling is that depending upon the Skilling policy, what they do is they
or their their desired capacity.
So as we have seen that in Step Skilling, it should launch three additional capacity unit vendors keep
utilization with a greater than 40 percent.
So in total, there would be four easy two instances that would be running.
So what the dynamic Skilling does is it modifies their desired capacity of your auto scaling group.
So if for easy to instanced needs to be running, it will achieve their desired capacity to forward.
And this is why it's refought as their dynamic skilling.
It changes their desired capacity based on certain metrics that it's been specified.
So that's behavioral or view about dynamic skilling.
I hope this video has been informative for you.
And I look forward to seeing the next video.