Note: This blog post is from 2016. Some content may be outdated--though not necessarily. Same with links and subsequent comments from myself or others. Corrections are welcome, in the comments. And I may revise the content as necessary.
Continuing my
series of posts on CF2016 which I started last week, I wanted to pull together a post on its pricing. Here I show both the base price (for someone purchasing from the US, in Feb 2016), for CF Standard and Enterprise, as well as the upgrade price from CF10 and 11. I also answer a few common questions (where I could find the answer), and I end by pointing to a currently available discount price for CF.
[....Continue Reading....]
If the licence is per core assigned to a VM, could any licenced cores not used be assigned to other VMs (a) running on the same host, and (b) running on a different host that's serving the same clustered website?
It would be useful if there was a CF Ent licence with fewer cores at a lower price. Not every installation is going to use loads of cores. Sometimes just 2 is sufficient for its purpose. Sell it in packs of 2, not 8.
And I suppose you're asking because you hope I might have some "in" to get you the answer, or perhaps that Adobe will see it here. We just can't expect either to be the case.
That's why I also said, in the middle, "As for the definition of "cores" and more, please, PLEASE see the EULA for more details, and indeed direct your questions to Adobe on licensing and pricing for such things as discussed in this section."
All that said, I do see your point that if the license is "per the CPUs/cores on the VM host", but you have only one VM guest running CF, and that running a limited number of CPUs, it would be odd to have to license things per what's on the host. But IANAL, and to answer your first question (which I realize was in jest), no I do not work for Adobe.
Indeed, I realize now that I failed to offer some useful info that does specifically give you the way to GET THE ANSWER you seek. In the original Adobe post on CF2016's release last week, Rakshith (the product manager) did say in more than one comment that he welcomed anyone contacting him with questions about licensing (or concerns over CF's vitality or Adobe's continued support of it, etc.)
His address is [email protected]. Again, he offered that publicly in the comments, so not inappropriate for me to be sharing here.
Hope that helps. And really, folks, if you do have more such questions (of a sort that I can't answer, and especially if it's about interpreting the EULA, etc.), please do direct those to Adobe.
Certainly if anyone learns something that they then want to share with others, I welcome such comments. Again, what I wanted to avoid here was the ongoing diatribe of complaints and debates about these things. I'm just tired of them, as there are often many, many perspectives to be considered, and some folks tend to focus only on their own.
I just want my blog to be about presenting information, not being an avenue for folks to vent frustrations. The Adobe CF forums, twitter, slack, and such are fine places for that.
We are thinking of moving from CF but maybe Adobe will continue getting it to parity.
Thanks for your insight
er