Hey, everyone, and welcome back.
Now, in today's video, we are going to discuss about the license manager service.
Now, generally in the enterprises, software licensing based management is one of the challenges that
you will generally face.
For example, enterprise might have a variety of software licenses, for example, for operating system
license.
They might have Windows license, red hat license, maybe for database, they might have Oracle, Microsoft,
SQL, SAP license.
And so many other third party licenses are involved.
Now, generally, in such cases, this introduces certain challenges.
So generally in cloud, we know that new servers can be launched in a click of a button.
And let's say that you have a license for two servers and you launch three servers or maybe ten servers.
Then it comes as part of the license violation.
And license violation detected during the audit process can lead to very heavy penalties for enterprises.
And this is one of the reasons why you have to ensure that you remain within your license requirements.
So you have to ensure that you track your licenses regularly.
Now, one of the challenges, as you are discussing for enterprises is that they don't really have one
account or two or three account.
It can be 80, it can be 100, it can be 158 accounts.
So when you have so many accounts, so many easy two instances being created by different set of teams,
one of the primary challenges that comes is related to the overall license management.
And in order to overcome this, ADA has introduced the license manager service.
So at a high level overview, the license manager is a service which allows us to manage license from
wide variety of software vendors across tablets and on premise.
So this can be explained with this specific diagram where a user is trying to launch two easy two instances
from Red Hat nine and eight.
Bliss immediately gave back an error stating No, we only have one easy to license of Red Hat nine.
So based on the licensing that you have available, the license manager service can also enforce the
policies.
So in the second point, we are discussing precisely that, that the enforcement of policies for license
based on various factors like CPU sockets, etc. can be applied by a database.
So this is the high level overview.
Let's have a quick demo.
So for today's demo, currently I'm in the license manager service and we have one license scholar's
expensive software license and within are easy to console.
We also have one server that is running using this expensive software now within here.
It basically also shows you the license type.
And this license type is based on CPU and it is also showing you licenses consume which is one out of
one.
So one license was present of this expensive software and this one license has already been consumed.
Now if I'll quickly open this up, the license manager service will also give you the exact easy to
instance details who is using this specific license.
Now, as we're discussing that this license manager based policies can also be enforced.
So let's do one thing.
Let's go ahead and try to launch one more easy to instance, based on this expensive software.
My.
So I say launch more like this.
And the expensive software easy to hyphen two.
And I launched the instance.
All right.
So we have to add a keeper.
Let's say proceed without a keeper.
I'll try to launch an instance and immediately.
You see, we got an error stating that the license configuration license count limit has been exceeded.
Great.
So I hope that this at a high level overview, you understood the benefits of license manager service.
Again, one important part to remember is that it's not just that the license manager can drag the license
of one account.
If you have 108 accounts, it can also drag the resources on all of the 108 accounts and the policies
can be enforced.
So that's the high level overview.
And with this will conclude today's video.