Re:Chef extends open-source licensing to all its software
by sytse on Tuesday April 02, 2019 @09:38AM
(#19553899)
So on one hand all the software will be open source and on the other hand there will be no free as in beer distribution anymore. Sounds similar to the RedHat model. I wonder if the community is active enough to produce a CentOS like alternative distribution for Chef.
The Essentials distribution is interesting, I wonder what is in it. I assume it will not have things like Role Based Access Control (RBAC).
Re:Chef extends open-source licensing to all its software
by holoway on Tuesday April 02, 2019 @09:45AM
(#19553971)
Original author of Chef here (although no longer with the company day-to-day). I would not assume that - 100% of the software Chef produces is open source, so no reason to ever differentiate on features in licensing. So I doubt they would remove anything.
Re:Chef extends open-source licensing to all its software
by bgoldy on Tuesday April 02, 2019 @10:00AM
(#19554133)
Correct - Essentials is just a low cost suite of Chef products. We offer two suites,. Effortless Infrastructure, focused on core config mgmt and security/compliance use cases and Enterprise Automation Stack which includes all of that plus a wide range of app automation capabilities including dependency mgmt, lifecycle mgmt, etc.
see pricing for the suites at https://www.chef.io/pricing/
Re:Chef extends open-source licensing to all its software
by sytse on Tuesday April 02, 2019 @06:17PM
(#19559113)
Cool! Thanks for following up.
Re:Chef extends open-source licensing to all its software
by geofft on Tuesday April 02, 2019 @09:40AM
(#19553919)
They call out RHEL specifically as inspiration:
> Beginning on April 2, we will be making all of our products open source under the Apache 2 license and we will begin to attach commercial license terms to our software distribution (binaries) with the next major release. This is very similar to the “open source product” model most effectively run by Red Hat®, where they develop software in the open while attaching enterprise license terms to the distribution of RHEL (Red Hat® Enterprise Linux®).
Q: What do I have to differently today than I had to do yesterday?
For our existing commercial customers there is no action required.
For existing customers using Chef for non-commercial purposes, experimentation, or individual use there is no change.
For contributors to Chef OSS projects, non-profits, and other special groups we are still working on how we will partner with those communities around licensing Chef products. Stay tuned for more info.
Everyone else can continue using our current releases in perpetuity – although they will be end-of-support in 12 months and no further bug fixes or security updates will be available for those versions without a commercial arrangement. Customers who choose to use our new software versions will be subject to the new license terms and will have an opportunity to create a commercial relationship with Chef, with all of the accompanying benefits that provides.
Q: How will this impact existing customers?
For existing customers this change will not impact their usage or contracts. Companies that already pay us for Chef Infra (formerly Chef), Chef Inspec, Chef Habitat and/or Chef Automate will continue to do so and we will continue to increase the value of their relationship with Chef.
Users who do not pay Chef today (use our free open source binaries), and net new users, will have three options going forward:
We will make licensing accommodations for individuals and significant community contributors to continue to use Chef Infra, Chef Inspec and Chef Habitat in the same way that they have been. In addition, we want to make it equally easy to experiment and self-learn with our various products.Finally, we will have a low cost “Essentials” suite of our commercial distributions that should satisfy the needs of smaller businesses.