TurboActivate and cloud machine (e.g. Amazon EC2)

Hi there,

We just bumped into an issue with TA and Amazon's EC2 cloud. One customer has got our software hosted on such virtual machine and obviously TA thinks it's a different hardware every time machine is reinitialized. Since the process is kind of automated I can't really expect them to deactivate each time before this happens and they can't activate again due to activation limit (which I obviously want to keep 😉 )

Any ideas how to solve the issue?

Well, the actual solution is to use TurboFloat -- but it's still about a week and a half away (providing no showstoppers pop up). TurboFloat allows customers to run on virtual machines like Amazon EC2 without running into problems like this.

In the meantime the best solution is to have your app automatically deactivate when it shuts down. Just do it for this one customer.

Does that help?

Hmmm, I don't like this workaround, one of the reasons is that if server goes down it won't deactivate. Obviously it's not possible to do that on startup.Would it be possible to have some kind of flag for the activation process to force deactivate the oldest active license?

Would it be possible to have some kind of flag for the activation process to force deactivate the oldest active license?

No. That defeats the purpose of hardware-locked licensing.

Hmmm, I don't like this workaround, one of the reasons is that if server goes down it won't deactivate.

Right, it is a crummy workaround. TurboFloat will solve the problem. We're working to get it out soon.

How about setting this up on "your" side (Lime). Meaning that I could mark a customer as allowed to overwrite existing activation? Or maybe other ideas? 🙂

I believe that TurboFloat will serve its purpose but I'm not really sure if I want to use it since such customers will be <1% of all and we already had hard time integrating TA with our app (since the app is hosted inside magical java app running on tomcat, loaded/updated through OSGI in some multitenant environment) so that's why I'm trying to figure out a different approach 🙂