Hi, everyone, and welcome back.
Now, in the earlier video we were discussing about the basics of license manager service.
In today's video, we are going to go ahead and implement the licensing related rules and see on how
exactly the policies are enforced.
So currently I am within the easy to console within.
Let's quickly open up the license manager service now within the specific service under the self managed
licenses over here.
Let's go ahead and quickly create a new manage license.
Now within the license name, you can just call it as expensive software and the license type is important.
So you have based on VCP scores, sockets as well as instances, so many of the softwares are logged
based on the number of CPUs or number of sockets.
So depending upon your license, you can go ahead and select the appropriate one for today's video as
part of testing will be logging based on the CPU and the number of CPU.
I'll just add it as one and we'll click on this checkbox to enforce the license limit.
Once this is done, you can go ahead and click on Submit Grid.
Now, at this stage, our expensive software license is available.
Now if you'll click over here, you have an option of Associated AMS.
So within here you can add an AMA based on which a license can be enforced.
For example, let's say you have two licenses of Red Hat, so you can add an AMA associated with the
Red Hat nine so that only two AC two instances can be launched based on the licenses that you have.
So let's do one thing.
Let's quickly launch a new ESI two instance.
I'll say expensive software, easy to.
Let's go a bit down.
Within the keypad.
I'll just say proceed without Kip and let's launch this.
Easy to.
Great.
Now, what we are going to do basically is that we are going to take an army of this specific, easy
to instance, and then we'll be adding that army under the license manager, and then we'll see if license
manager enforces the limits when we try to launch more easy to instances which breaks this VCP limit.
All right.
So our instance is running.
Let's click here.
And let's create a new image from this.
You can say expensive hyphen image and will create an image.
Alright.
So our e-mail is getting created.
Let's quickly open this up.
So if you will see the status is still pending, it can take a few minutes for the AMA to be up and
running.
So let's pause the video and I'll resume once the AMA is ready.
All right.
So it has been a few minutes and our AMA is ready.
If you look into this status.
The status is now available now from the license manager service.
Let's associate this new AMA.
So our AMA is appearing over here.
I'll select it and I'll click on Associate.
And now you have option to either associate it across accounts or associated with only this account.
So I'll click on associate with only this account and I'll click on Confirm.
Now at this stage, if you look into the resources, there are no resources that are currently available.
So no ESI.
Two instances are running based on this AMA.
So let's go ahead and launch easy two instance based on this AMA.
Now within let's just call us licensed ESI two.
Now one thing to note is that the VCP use in use is zero out of one, so maximum of only one VCP can
be used.
Now if you try to launch an easy to instance based on two views for an example.
So two micro is based on only one CPU, but there are instances which uses to visit you like PT to medium
or any other instance.
So let's go ahead and use data medium, which we know that it will break our licensing rules that we
had created.
Once this is done in the keeper, you can just associate a keeper or you can say, proceed with our
pipette and let's try and launch an instance here.
And immediately, you see, we got an error stating that the license count limit has been exceeded.
So this is working as expected.
Now, let's try to have a best case where we just launch a easy to instance.
Which is based on only one CPU.
Right.
Once this is, then let's launch the instance here.
And as expected, are instances running and our license easy to status is now in the running state and
for the license manager.
If I refresh this page.
You see it states one out of one CPU in use and it is also showing us under the track resource the instance
of the easy two instance that is using the expensive software AIMA It will competence inside it is 2d0
and the same.
You can see warrior grade.
So I hope that this you understood practically related to how you can enforce the policies using the
license manager.
Before we conclude again, do not forget to terminate the AC two instances that you have created for
this practical to avoid any unexpected cost.
So with this will conclude today's video.