How manage licenses for software running in OpenStack clouds?

asked 2014-12-30 05:30:26 -0600

Ravi J Sharma gravatar image

updated 2015-01-04 19:27:11 -0600

smaffulli gravatar image

Is there any licensing model available that can be used while migrating a node locked or site locked software application from a non-cloud platform to a cloud platform (like openStack platform) which can address all the concerns addressed by site/node locking license model. Is there already any discussion or development happening in the forum for node/site locked licenses?

The background is that as a software vendor I want to restrict the usage of my software by a customer to a particular cloud (owned or managed by customer) through licensing.
In non-cloud/non-virtual environment, there are some unique numbers/Ids (e.g. MAC-IDs) which are used to identify a server uniquely and as a software vendor, I can provide licenses to my customers on the basis of that unique-Machine-id, so that usage of that software is restricted to the concerned host server(s) only.
In cloud environment (due to virtualization), I could not find any such identification parameter which can be used in licensing to restrict the usage of the software to a particular cloud. That is why I was exploring whether there is any licensing technology already developed or being developed to fulfill above mentioned requirement.

edit retag flag offensive close merge delete


Consider editing your question to be more specific: I can't really understand exactly what you're trying to do.

smaffulli gravatar imagesmaffulli ( 2014-12-30 19:17:12 -0600 )edit

3 answers

Sort by ยป oldest newest most voted

answered 2015-01-05 03:31:43 -0600

Ravi J Sharma gravatar image

Thanks trung-t-trinh and don for the answer. I explored a bit and found that UUID can be overridden in virtual machines in similar fashion as it can be done for MAC-id. This defeats the purpose of license and one can force a virtual machine to use a particular UUID and MAC-id and can use (or rather misuse) the licenses bound to such IDs.

edit flag offensive delete link more


although the UUID can be overridden, you can only have 1 in a given cloud (its cloud-wide unique), so the risk is reduced. the physical mac address is trivially overwritten on a real machine outside of virtualisation, so its not over strong either.

don gravatar imagedon ( 2015-01-05 07:58:59 -0600 )edit

answered 2015-01-04 16:33:30 -0600

don gravatar image

I would consider using the instance UUID. It will be unique, its no more cloneable than a mac address. Its accessable from the instance (either as a bios parameter, see e.g. dmidecode) or from the metadata.

edit flag offensive delete link more


Would it remain same if the virtual machine instance is migrated from one compute node to other (in case VM migrartion)?

Ravi J Sharma gravatar imageRavi J Sharma ( 2015-01-05 00:44:50 -0600 )edit

answered 2015-01-05 00:39:40 -0600

trung-t-trinh gravatar image

It would be better to combine both VM instance UUID and the MAC of the computing node on which the VM instance is launched.

edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools



Asked: 2014-12-30 05:30:26 -0600

Seen: 440 times

Last updated: Jan 05 '15