How to know how many floating license are leased currently?

Floating Licenses
#1

Hello,

Is there any way to know how many floating license is leased, and by whom - either via API or with special tool?
Because, when user tries to launch our app, and all floating licenses are leased, they want to know who is eating up all licenses.
So, they can unlease unnecessary clients to free up for urgent/high prioritized clients.

How can I achieve such workflow? If there’s no such feature, is that possible for you guys to expose it via API?

Please let me know.

#2

Currently the only way to know that is using the log file generated by the LexFloat server.

We would love exposing an API for the same, will add that feature in the next release.

#3

Thank you very much for adding the API. When will be the next release currently planned?

#4

As for API, also it would be nice to have a method to know how many licenses can be leased from the LexFloatingServer. Because we’re thinking to use floating license for automated case - launch a task from program if slot (floating license) is still available - so we need to know if free slots are available via API.

#5

Also, please add a API to know when the expiration date of the floating license server. So we can show users when the expiration date is for heads-up.

#6

Do you mean the expiration date of the floating license server key or the license leased by LexFloat Server

#7

Do you mean the expiration date of the floating license server key or the license leased by LexFloat Server

"the expiration date of the floating license server key "
Because, it requires some actions by our customers (to renew/extend license) so they want to know when it will happen before it happens.

#8

Also, if you guys know roughly when the next version will be released, please let me know.

#9

We are planning a release by the end of third week of December.

#10

Sounds good! Looking forward to using new APIs.

Thank you very much for your support

#11

Hi,

We have implemented the stats api, please have a look at the response, if it suffices:

{
“availableLicenses”: 9,
“totalLicenses”: 10,
“daysLeftToExpiration”: 365,
“leaselength”: 60,
“floatingClients”: [
{
“ip”: “192.168.2.3”,
“leasedAt”: 1480702017
},
{
“ip”: “192.168.2.4”,
“leasedAt”: 1480703123
}
]
}

#12

Looks good!
Some quick question,

  • what is the “format” of leasedAt?
  • Is “LeasedAt” the last time lease happens?
  • “LeasedAt” date/time info is NOT local-time based, it is UTC based, correct? (because, API caller will never know server machine’s local time settings)
#13

leasedAt - is a unix timestamp - UTC based
It is time at which the lease was granted and not refreshed.

#14

It is time at which the lease was granted and not refreshed.

Got it. It is good to know when the lease was granted.
But also, in case of Zombie License happens, it would be nice to know when the current lease will end, I think.

#15

Also, it would be nice to know when Grace Period is started (or when it will end)
So we can detect if the Floating Server got into a problem before Grace Period ends. (In case of the Floating Server is disconnected from Internet and no one noticed)

#16

We can add a new property for the same, leaseRefreshedAt which can be used to compute the time.
For graceperiod will add a property too.

#17

That works to me. :slight_smile: Thank you.

Also, please ping me in discussion thread when the new SDK with the API set is released. I will try it out.

#18

You receive SDK update mails automatically. LexFloatServer v2.4.0 with the above API was released three days back.

#19

oh really? Probably Sales team who subscribed the plan got the email… I will ask them.
Thanks!

#20

Hello,

I downloaded v2.4.0 from following page, but LexFloatClient nor LexFloatServer does not seem to include new API…
https://cryptlex.com/app/api
(I checked windows version)

Is it possible to double check if v2.4.0 is the one including new API? Or if I missed something, please point out which API I supposed to use to get that information.

Best,