Here you are.
And welcome back.
Now, in today's we will be discussing about the basics of easy to feed, knowing the future of EU fleet
was launched.
It basically allowed users to launch a fleet of sport instances that spans easy to instanced types and
availability zones without having to write custom code to discover capacity or even monitor prices.
Now, let's go ahead and understand this with an example.
So let's say that you have a chunk of data that you need to analyze now in order to go ahead and analyze
this data.
There are certain set of two instances that are required.
So what will be assuming here is that in order to perform a complete analysis, you require a total
of 16 weeks.
So you will see you have four Ekta instances and each instance has four VCP available.
Now for the 16 VCP used to be available, there are multiple instanced types that can be used.
So you can use one instance type of Sieff either for X Light, which provides 16 Ekpo, or you can use
two instances of C failure to explode, which provides eight VCP each.
Or you can use for instances of C fadeout exclosure which provides for VCP each so you can use multiple
set of X2 instance Pape's to go ahead and achieve your goal of 16 C.P.U that is required to analyze
the data that you have now.
When it comes to spot instances, each one of these can have a different pricing page.
Now one of the challenges that used to come is you have to write a custom code if you want to either
discover the capacity, whether each one of them is available and if available, how different they
are when it comes to prices.
So it should not be like the fourth, if not X.
Large instances are much more cheaper than a single C fighter, for instance.
If falsified, X instances are cheaper and are fulfilling the VCP requirement and you go with the C
Phytophthora, then ultimately you are paying a higher amount of money.
So in order to overcome this, what is it?
It allows you to do is it allows you to go ahead and say wait.
So what you can do is you can set a weight associated with each one of the instance.
For example, let's say that since C Vedat for X large is providing 16, you you give a rate of 16 C
failure to explode, which provides eight VCP each.
You give a bit of it and see fadeout explode, which provides for VCP, you give a bit of effort.
So this is the first step.
So if you look into how exactly can we define it within the easy fleet, you see, you specify for instance,
and you said associated with that capacity of 16, 18 for now after you have said the appropriate way,
the next important step is to set the target capacity.
For example, let's assume that you specify that you have a target capacity of 16.
So what the EU fleet will try to do is it will try to launch a set of instances in a way that the overall
weighted capacity becomes 16.
So either it will launch one of the four declared two of the two or four of the excellent know which
one of these three it will launch totally depends upon the overall pricing.
So easy to will select the most cost effective combination of instant status and availability zones,
and then it will launch the instances accordingly.
Sometimes it can happen that the C five forex led is much more cheaper.
Then it will launch the C forex that sometimes it can happen that as if a set of four instances of Ceefax
that is much more cheaper than that of several forex slides.
So in such cases it will go ahead and launch the four instances of C failure takes time.
So this is what is it allows us to do at a high level overview.
All right.
So just to reverse the easy Duflot attempt to launch the number of instances that are required to meet
the target capacity that you specify within the fleet request.
So, for example, you're within the total target capacity.
You have specified 16 now.
Also known that fleet can comprise only OnDemand instances, only spot instances or combination of both
on demand as well as both instances, depending upon the configuration that you mean.
So if you look into the sample configuration, the total target capacity is 16, OnDemand target capacity
is four and spot incidents target capacity is eight.
So what would typically happen is either it will go ahead and launch the fight or two instances as part
of a sport or it will go ahead and launch failure to explode so that it meets the sport target capacity
of it.
Now, since OnDemand target capacity is only four, it will go ahead and try and launches.
I thought exercise based in Stancil or light, so I hope at a high level overview, you understood the
basics of Duflot and you should also be able to quickly interpret the requirements based on the specification.
So based on the specification, the total target capacity is 16.
So it basically means you want six CPU's on demand target capacities eight.
So eight weeks you should be fulfilled using only one instance and then spot target capacity is eight.
That means it BCB.
You should be using this for instance, type.
So all of the combinations is something that also you can trade on.
Now with this, let's go ahead and have a quick demo so that we can understand it in more detail.
Now, within the easy to instance, I have a file called As a Friend or Design.
So within a year you'll see that there are three instance types that are defined Aurier and each of
the instance type has its associated weighted capacity of one.
So you have Scevola Seadrill identified at large and within the target capacity specification, you
specified that the total target capacity should be one and the default target capacity type esport.
So what the EU fleet will do, it will go ahead and launch one sport instances among these three considering
the overall price.
So let's go ahead and try treating it so I'll take it easy to create fully specified charges on file.
So this will go ahead and create a fleet, so now it has given us a fleet.
So let's look in two, which is the instance type that it has launched now within the eco console,
we currently have one instance that is running from where we are running the EU fleet.
Come on, let's refresh this page.
And now you see one more instance of Type C 3.0 that has been created.
Now, this instance would be based on spot.
So under the lifecycle, you see, this is a spot state that is created.
Now, along with this, I also have one more file for today's demo.
So let's look into it.
So similar to the previous file, you have three CEDO instance, each one with its associated weighted
capacity of one.
No wonder the target capacity specification, the total target capacity is to within your OnDemand target
capacity is one and the spot target capacity is one.
So what it will do, it will go ahead and launch two easy two instances, one based on on demand and
second based on spot.
So let's go ahead and also try it out.
So similar to the previous command.
Let me go ahead and run this command.
This thing, it should go ahead and create.
We see two instances.
So within the easy to cancel.
Let's refresh the page.
And at this moment, you have one easy two instances that is creating the lifecycle esport.
So let's quickly wait for one more moment.
So, Naifeh, refresh the page.
Now, you see the total instances that are now running is four.
So one would be based on the on demand.
So you have one see federalised instance that was created.
Let's look into the lifecycle.
It is normal.
So this is a OnDemand instance tape that was created.
Great.
So with this, I hope at a high level, or do you understood the basics of Exito fleet, depending upon
the requirement to fleet will go ahead and create a set of instances keeping the overall cost in mind.
So with this will go ahead and conclude today's video.