This very good news! I am not sure the documentation made this clear. Or perhaps I mis-read it.
Obviously I was in error of my understanding on the current system. I am sorry if I was overly critical. I am sure you realize the importance of this, which is why you already implemented something like what I was requesting. Thanks.
So how often does the local license server re-borrow the licenses? The important question being: What is the minimum amount of time we will ALWAYS have available (once the licenses are borrowed)? I am hoping that it gets updated daily and extended for another two weeks or whatever so we always have those two weeks.
Also with the local license server re-borrowing on a regular basis I assume this can be done even when the licensees are in use, right? To borrow manually the licenses can’t be in use.
Thanks for clarifying all of this.
I do now see that the doc page has been comprehensively reworked, making it actually much clearer than it was when I had my problems a while ago.
That page was most certainly not clear and definitely (at least for me) suggested that it was not an automatic process and that we had to remember to re-borrow licenses periodically.
So hopefully now everyone can be assured that if they borrow their license once for any machine, then that will be the only time they need to do it.
Barring an EMP event of course
Joking aside, why is the ‘last 3 days’ thing relevant?
Wouldn’t it be possible/desirable to shorten that time so that it checks daily and simply advances that 2 week borrowed period by one day each day it checks?
The License server will try to reborrow (extend the offline usage of your licenses for 2 more weeks) on the 11th day, from when the first borrow was done. The License server will continue with the borrow attempts for 3 days, you will require an internet connection once during that time. The borrow process should be quite fast. You will be able to use the licenses for the whole 2 weeks, if your internet connection fails for the last 4 days in a row - you will lose the license usage.
The license server will reborrow the exact same amount of licenses you borrowed the first time. If you want to add more or release some of the licenses - you will have to do this manually.
I will send your feedback to our Documentation team. I agree that our documentation was kind of messy in the past, but we have been really trying to improve in that department.
If your license server has, even sporadically, an internet connection, the reborrowing process is automatic. We have implemented a way for a machine, that is totally off the grid, to act as a license server. In that situation, you will have to do the reborrowing process manually.
Constant checkups might degrade the license service and cause new issues for people with high number of licenses. We are aware that the process is clumsy and are working on ways to make your life easier. To give an example, longer borrowing periods are in the works and might be available soon.
It was positive feedback, just to make clear
I only looked at it again because of this post and it is now very clear, so good job on that.
And I know that you have a big job on your hands to update the documentation. The improvements are obvious.
So when I’ve done this initial borrowing I will never have to think about it again as long as I’m connected at least every 12 days? I have no floating licenses.
Is there a reason not to auto renew the borrowing more frequently? With the current setup we end up with only three days at the end of cycle. Power outages, Internet outages, attacks, routing issues, etc. have all been known to last that long.
Could you not auto renew every day, or at least keep a minimum of one week in reserve? It’s not like it uses much bandwidth at all, perhaps a little CPU for some crypto hashes, but not much in terms of resources.
Also, sure would be nice if the local license server could send out an email if it fails to renew (even one failure we would want to know about). Mail server is local, so we get that email even if internet is down. (Which is rare since we have a backup connection.)
Our backend servers will be constantly spammed by auto-renewal requests. This will degrade the service for all people. Please note that we have stated that V-Ray requires an internet connection to be used. We also understand that this is not applicable in all situations, this is why we have implemented the offline option. We are constantly trying to improve this feature and will continue to do so. I will talk with our developers about the suggestions you gave us.
As a developer and network guru, I understand your concerns and thank you for the reply.
Perhaps once a day is too frequent, but every week might work out. You could look at reducing your network load be shortening the data sent and replied. ZLib or STACK compression is also very easy to implement these days, so perhaps things could be compressed without a lot of effort.
You say the servers would be spammed with auto-renewal request, but how about all the spam you get form people who do not borrow their licenses? You get CONSTANT spam form *most* users (since most people don’t look here and have no idea that if their internet drops they lose VRay entirely). Instead, perhaps alter the installer as suggested [somewhere by someone, can’t find it, I apologize for not attributing credit properly] such that it offers to setup the local license server to borrow the licenses when installing. This way you significantly reduce your network and server load, and users are happier because they don’t bitch and moan when they lose the license when their internet goes out. Right now, you get a checkout request every time someone opens the freaking Render Settings window, or hits render. Or one from each render node every time someone renders. All of these could be quelled by settings users up with a “normal” local license server that checks out licenses rather than check in with your servers for every request. If you offered this at install time I think at least half of users, and well more than half of render nodes users would select it.
Alternately, just increase the borrow period form two weeks to three. Then you get the exact same amount of load on your servers, but users always have ten days (which is reasonable).
Again, you really have to remember licensing is to keep honest people honest. There are plenty of places where people bypass all of this illegally. You know it is going to happen, and you can play cat and mouse putting license checks all over the place. The only people who suffer are the paying customers who want to support Chaos. People looking for free software will just deal with the problems, and they obviously aren’t going to complain to support. The goal is to make it a big enough pain that people will be honest and pay for the software without driving away paying customers. The default settings of failing if the internet or Chaos servers are down I think WILL drive away paying customers, which is why I am again repeating that increasing the borrow time (or time out with the auto-renew) and informing users of the always on internet requirement without borrowing at INSTALL time is critical.
You saw how much I freaked out when I learned about it. Hell, I referred to it as a “design flaw” in some thread (sorry about that). You guys/gals/theys obviously put a lot of thought into this, because it wasn’t a design flaw at all. You already thought about it. You just didn’t notify the user during the install of the risks of not borrowing the licenses.
Just please think of a way to give us all ALWAYS a minimum of one week and I will stop posting to this thread
Other possible load reduction techniques include assigning each license server client (as in client to your servers) a discreet time of day for contacting your servers each day (week, etc.)
You keep a database and round robin out these times to all the users’ license servers so that no more than 1/2880 of users contact your server at one time. (2880 is the number of 30 sec intervals you have to work with per day). This is if you assigned each user a spot every :30sec. So when people borrow a license you query your database of times already allocated (N+ 30 sec) and select the slot least used and assign it to that license server. Or break it down into 15 sec intervals, even… I doubt it takes that long to process a request for a few nodes. You could break it into 5 sec chunks. The user’s local license server only re-borrows at the prescribed time. Sure clocks vary, but you will end up with a much more even load, FAR more even than 40 render nodes hitting your servers at once for those who have not borrowed their licenses.
The goal is to take the auto-renewal load and spread it out so it is nothing to worry about. Since this is something you have total control over it should be easy to manage. In theory of course
Again, thanks for listening. I see a lot of effort has put into licensing, and I thank you and your team for that. I am just an ideas guy, and some of those ideas may be crap (a lot of them, I am told), but perhaps one of them makes something go “click” for you or one of your team. Then all my rambling has proved useful… Maybe
Again, than you for listening. This is what sets Chaos apart from a lot of companies these days.
Another simple option would be to extend the borrow period. You still auto renew 11 days in but users get 18 days per borrow. Now you have no additional server load and we have a week of the licenses we are paying for, even in the event of outages. All of this at the expense of changing one constant in a header file
Well, I just got bit by this pretty good mid-sequence render. And I can’t work interactively either. Just lost internet due to the weather and now I can’t do much. If this happened in the middle of a paying job vs a personal project, I’d be screwed. Maybe recurring borrowing license is the way to go, but too late to save my day.
