tracker issue : CF-4203085

select a category, or use search below
(searches all categories and all time range)

EULA doesn't cover container/Docker scenarios

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/Fixed

Reporter/Name(from Bugbase): Bradley Wood / ()

Created: 07/17/2018

Components: Documentation, EULA

Versions: 2018

Failure Type: Others

Found In Build/Fixed In Build: Final / NA

Priority/Frequency: Normal /

Locale/System: / Platforms All

Vote Count: 5

It is not currently clear how Adobe intends to allow for containerize/Docker installs of ColdFusion.  The EULA mentions only physical servers and VMs.  While the EULA's definition of a VM is rather vague it is not standard in the Docker world for a container to be conflated with a VM.  

Also, how will core-based licensing change to cover As-A-Service sort of arrangements where you have little knowledge or control over the host.  For instance, I can run ColdFusion on Heroku, but I have no control or information really about the physical or virtual machines that power my dynos.



Hope these links help:
Comment by Vamseekrishna N.
29316 | July 18, 2018 04:01:22 AM GMT
Thanks for the links Vamsee. Even when Googling for an answer, I had not come across these page. I'll reproduce the text here for anyone coming to this ticket. it is the same verbiage for both Enterprise and Standard licensing: ====================================================== How do I license ColdFusion on containerized deployments? Every containerized deployment needs to be licensed as per the ColdFusion End User Licensing Agreement (EULA). For instance, if ColdFusion is being deployed on two containers on a single VM instance, then both containers running ColdFusion will have to be licensed separately as per the ColdFusion EULA based on that VM instance being used. ======================================================
Comment by Bradley W.
29317 | July 18, 2018 04:37:26 AM GMT
So this makes using CF standard or enterprise un-tenable within container infrastructure without some sort of "special" arrangement with adobe on licensing. The only way a container makes sense in light of this licensing decision is as an evaluation tool. You may as well not bother developing it further as I cannot see how anyone can use it.
Comment by Doug C.
29354 | July 19, 2018 08:18:57 AM GMT