Language Selection

English French German Italian Portuguese Spanish

Chef Liberated

Chef Goes All-In on Open Source

  • DevOps Chat: Chef Goes All-In on Open Source

    In front of next month’s ChefConf in Seattle, Chef has announced a major refinement to its business model. Affirming and clarifying its commitment to open source business models, Chef will now and in the future release all of its software as open source.

LWN and original from Chef

  • Chef becomes 100% free software

    Chef, the purveyor of a popular configuration-management system, has announced a move away from the open-core business model and the open-sourcing of all of its software.

  • Introducing the New Chef: 100% Open, Always

    Today, Chef is announcing meaningful changes to the way that we build and distribute our software. Chef has always believed in the power of open source. This philosophy is core to the way that we think about software innovation. There is no better way to build software than in the open in partnership with individuals and companies who use our stack in the real world. And for enterprises and other organizations facing complex challenges, Chef backs up our software by building and supporting distributions for our projects with the resources necessary for these organizations to succeed.

    Going forward, we are doubling down on our commitment to OSS development as we extend our support for the needs of enterprise-class transformation. Starting today, we will expand the scope of our open source licensing to include 100% of our software under the Apache 2.0 license (consistent with our existing Chef Infra, Chef InSpec, and Chef Habitat license terms) without any restrictions on the use, distribution or monetization of our source code as long as our trademark policy is respected. We welcome anyone to use and extend our software for any purpose in alignment with the four essential freedoms of Free Software.

Chef-paid 'analysi' comments

  • Chef’s Different Recipe

    Over the course of the past three plus years, the market has seen a growing number of commercial open source organizations – with encouragement from some investors – drifting away from traditional open source licensing and norms. While there have been significant differences in the precise mechanics of their respective approaches, the common thread between the likes of Confluent, Elastic, MongoDB, Redis Labs and TimeScale has been their willingness to violate open source norms long considered sacrosanct.

    Contrary to internet opinions, however, little if any of this was done with malicious intent, or absent due consideration for the grave implications of the various moves. In the majority of cases, the difficult decisions were made reluctantly, under duress. Whether that duress was real or more theoretical in nature is a matter of some debate, but there can be no doubt that the companies involved embarked on these courses because they felt they had to, not because they particularly wanted to.

    There have been many contributing factors to this drift away from open source, including the intrinsic problems of compelling payment for assets otherwise available for free, but by far the biggest driver has been the once cold war that recently escalated into a full scale hot war between cloud vendors and commercial open source providers. The relationships between these archetypes is fraught, and has evolved from relatively benign indifference on the part of open source providers to existential, unmanageable dread.

By Sean Michael Kerner

  • Chef Opens Up DevOps Platform With Enterprise Automation Stack

    Chef has been at the forefront of the DevOps movement with its namesake open-source Chef project. Not all of Chef's platforms, however, have been open-source, with some available under commercial proprietary licenses.

    On April 2, Chef announced a major shift in its company alignment, making all of its products available under the Apache 2.0 open-source license and revealing a new supported platform called the Enterprise Automation Stack. The move to being 100 percent open-source is an effort to provide more transparency and encourage broader collaboration. Rather than moving the projects to an independent, third-party open-source foundation and governance model, however, Chef will continue to lead and operate the projects.

    "When looking at foundations and the shape of open-source, a big issue is deciding who controls and builds the upstream asset. As soon as you put software into a foundation, the foundation controls the asset," Adam Jacob, co-founder and CTO of Chef, told eWEEK. "One of the things that we're doing is aligning our own commercial interests with our interest in being the upstream that provides the project."

Goodbye Open Core — Good Riddance to Bad Rubbish

  • Goodbye Open Core — Good Riddance to Bad Rubbish

    This morning, Chef Software announced that it will be releasing 100% of its software as Open Source, under the Apache License. Going forward, all of its product development will be done in the open, with the community, and released as Open Source Software. Chef is done with being Open Core, and is now a Free Software Product company. Good riddance to bad rubbish.
    As a Co-Founder of Chef, a board member, and a community member, I couldn’t be more thrilled. For me, it eliminates the longest-running source of friction and frustration from my time at Chef. On the one hand, we have a community that cares about the software, and about each other, where we develop the software in concert with our users and customers. On the other, we produced a proprietary software stack, which we use to make money. Deciding what’s in, and what’s out, or where to focus, was the hardest part of the job at Chef. I’m stoked nobody has to do it anymore. I’m stoked we can have the entire company participating in the open source community, rather than burning out a few dedicated heroes. I’m stoked we no longer have to justify the value of what we do in terms of what we hold back from collaborating with people on.
    As an insider, I got to witness first-hand the boldness and deep thought put in to this transition by the team at Chef. Our incredible CEO, Barry Crist; Corey Scobie, the SVP of Product and Technology; Brian Goldfarb, CMO; Katie Long, our VP of Legal; and so many others. Thank you.

Yet more coverage

Chef Goes All Open Source

  • Chef Goes All Open Source

    The Chef automation tool, a popular solution for DevOps IT management scenarios, has announced that it will be become a 100% open source platform. In the past, the basic Chef application was available in open source form, but the company also provided several enhancements and add-on tools with proprietary licenses. Rather than building proprietary tools around an open source core, Chef will now open source all of its software under an Apache 2.0 license.

    According to Chef CEO Barry Crist, “Over the years we have experimented with and learned from a variety of different open source, community, and commercial models, in search of the right balance. We believe that this change, and the way we have made it, best aligns the objectives of our communities with our own business objectives. Now we can focus all of our investment and energy on building the best possible products in the best possible way for our community without having to choose between what is “proprietary” and what is “in the commons.”

Configuration Management Tool Chef Announces to go 100% OSS

  • Configuration Management Tool Chef Announces to go 100% Open Source

    You are here: Home / News / Configuration Management Tool Chef Announces to go 100% Open Source
    Configuration Management Tool Chef Announces to go 100% Open Source
    Last updated April 5, 2019 By Ankush Das 2 Comments
    In case you did not know, among the most popular automation software services, Chef is one of the best out there.

    Recently, it announced some new changes to its business model and the software. While we know that everyone here believes in the power of open source – and Chef supports that idea too. So, now they have decided to go 100% open source.

    It will included all of their software under the Apache 2.0 license. You can use, modify, distribute and monetize their source code as long as you respect the trademark policy.

    In addition to this, they’ve also introduced a new service for enterprises, we’ll take a look at that as you read on.

"Chef Plates All Software as Open Source"

  • Chef Plates All Software as Open Source

    The IT automation and dev ops software vendors is embracing the open source model to clarify its product line and enhance its value proposition.

  • Chef says it’s going 100% open source, forks optional…

    Chef has lifted a page from Red Hat’s recipe book, and is making all of its software 100 per cent open source, under the Apache 2 license.

    But if you’re planning to use the automation and configuration specialist’s software in production, you’re still going to be expected to cough up for a subscription.

    Chef CEO Barry Crist said in a blog post today that the company “has always believed in the power of open source”.

  • Leading DevOps program Chef goes all in with open source [Ed: CBS repeats Microsoft talking points: "Some companies are wriggling out of open-source to maximize their profits." And proprietary software companies never do?]

    Some companies are wriggling out of open-source to maximize their profits.

  • “Chef” DevOps leading program goes all-in on open source

    Chef, one of the leading DevOps companies announced from here on out it would be developing all of its software as open source under the Apache 2.0 license and revealing a new supported platform called the Enterprise Automation Stack.

Some belated coverage

  • Chef open sources 100% under Apache 2.0 license

    “Chef Enterprise Automation Stack lets teams establish and maintain a consistent path to production for any application, in order to increase velocity and improve efficiency, so deployment and updates of mission-critical software become easier, move faster and work flawlessly.”

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

Events: OpenStack, Open Source Day (OSD), and Intel

  • OpenStack Keeps One Eye on the Prize, One Over Its Shoulder
    The OpenStack Foundation (OSF) used its recent Open Infrastructure Show (OIS) to remind the open source community of its importance, maturity, and flexibility. But the event also showed that the group understands that the virtualized infrastructure environment is evolving rapidly. I must admit that heading into the OIS event I was not expecting much. Conversations I have had over the past year continued to show a strong core of OpenStack supporters, but it seemed that the platform’s innovative spirit was diminishing. And in such a rapidly evolving technology segment, any sort of diminishing momentum is the equivalent of going backwards.
  • Open Source Day 2019 focuses on the cloud, security and development
    The 12th edition of Open Source Day (OSD) will take place today at the Legia Warsaw Stadium in Poland’s capital city. The event will include presentations, forums and nine technical sessions spanning automation, containerization, cloud computing, virtualization, security, monitoring, CI/CD, software and app development and databases.
  • Inspur and Intel share Rocky testing data at premiere of OpenInfra Summit
  • Intel hosts Open Source Technology Summit - OSTS 19 - Software - News
  • Intel Pushes Open Source Hypervisor With Cloud Giants
    Intel, along with cloud giants Amazon and Google, is working on an open source hypervisor based on the rust-vmm project. The chipmaker discussed this and several other open source efforts at its Open Source Technology Summit, which kicked off yesterday. The company “is and has been one of the largest contributors to open source,” said Imad Sousou, Intel corporate vice president and general manager of system software products. “Intel is the No. 1 contributor to the Linux kernel. We write 10% to 12% of the Linux kernel code.” For the record: Red Hat is No. 2, and it contributes about 6%, according to Sousou.
  • Open Source to trickle into AI and Cloud
    Intel’s Clear Linux* Distribution is adding Clear Linux Developer Edition, which includes a new installer and store, bringing together toolkits to give developers an operating system with all Intel hardware features already enabled. Additionally, Clear Linux usages are

Latest Openwashing

Google: TensorFlow, Open Hardware and More on Collaboration

  • Beginner's guide for TensorFlow: The basics of Google's machine-learning library
    It is an open-source, accelerated-math library designed to help developers build and train machine-learning models using a wide range of hardware — CPUs, GPUs, and even specialized chips such as TPUs (Tensor Processing Units). While TensorFlow was originally designed for use with more powerful machines, it has evolved to be able to create models to run in all sorts of unlikely places, from browsers to low-power IoT devices. Today, TensorFlow can be used with a wide range of programming languages, including Python, Go, C++, Java, Swift, R, Julia, C#, Haskell, Rust, and JavaScript.
  • Google extends lowRISC FOSSi partnership
    Unlike proprietary processors, the design and instruction set architecture (ISA) for which are kept behind a typically expensive licence wall, free and open source silicon (FOSSi) does what it says on the tin: Projects like RISC-V provide both the ISA and key implementations under permissive licences, allowing anyone to use, modify, distribute, and commercialise the technology without a single license or royalty payment - including, in many cases, the ability to create a proprietary implementation, should they so choose. Following on from the news that it was a founding member of the Linux Foundation's CHIPS Alliance, an industry group set up to 'host and curate high-quality open source code relevant to the design of silicon devices', Google has now announced that it is extending its existing partnership with the lowRISC project to include additional funding, support, and the appointment of two Google staffers as board members on the project.
  • Google wants an open source silicon community for chip design
    As evidenced by Android and Chromium, Google has long been committed to open source software. The company now wants to foster a similar community for hardware and chip design, particularly open source silicon.
  • To Create Prosperity, Free Market Competition Isn’t Enough—You Need Collaboration Too
    What’s ironic is that all of this communal activity isn’t driven by beret-wearing revolutionaries plotting in coffee houses, but by many of today’s most powerful and profit-driven corporations, who act not out of altruism, but self-interest. The fact is that technology firms today who do not actively participate in open source communities are at a significant competitive disadvantage. For example, Chris DiBona, Director of Open Source at Google, once told me, “We released Android as an open source product because we knew that was the fastest way to grow adoption, which enabled us to preserve the relationships with customers for businesses like search, maps and Gmail.” That is the reality of today’s marketplace. You collaborate in order to compete effectively. Businesses that don’t accept that simple fact will find it difficult to survive. Science’s commitment to communal effort is not at all new, but is a thread running deep in America’s long history of technological dominance. And it’s not all about private companies competing with each other, either: it’s about how the market can benefit from public investment. When Vannevar Bush submitted his famous report, “Science, The Endless Frontier,” to President Truman at the end of World War II, he argued that scientific discovery should be considered a public good crucial to the competitiveness of the nation. The crux of his argument is that such efforts build capacity through creating what he called “scientific capital” and pointed out that “New products and new processes do not appear full-grown. They are founded on new principles and new conceptions, which in turn are painstakingly developed by research in the purest realms of science.”

FOSS in Telco

  • The benefits of open source networking for enterprise IT
    Open source software has proved its benefits for various aspects of the IT community in terms of costs, agility and flexibility. Open source networking software is in its early stages of deployment among enterprises. Meantime, hyperscale cloud providers and the largest service providers have made effective use of open source networking. It is standard in large IT organizations to consider open source software alongside packaged software and SaaS as part of their IT architecture. Enterprise IT shops frequently deploy open source software in test environments and when designing new applications, like in DevOps. IT organizations report a range of benefits from open source software, including innovative design, time to market and agility. While open source software helps reduce some costs, deployment in production environments is generally accompanied by a vendor-supplied support contract.
  • How “Lab as a Service” supports OPNFV and ONAP development
    The Interoperability Lab at the University of New Hampshire (UNH-IOL) is a community resource that allows developers and open source users to have access to resources that they might not have themselves. The “Lab as a Service” provides the necessary shared compute and networking resources for developers working on projects such as OPNFV. Access is remote via a VPN connection, so it acts like a remote server. Those new to OPNFV can create a virtual deployment on a single node and run small VNFs on top. It gives developers access to a bare metal system for low level checking and installs. The next step is to add better support for multi-node usage, integrating the CI work that's being done in the OPNFV project and making the system more compatible with ONAP development.
  • The modern data center and the rise in open-source IP routing suites

    Primarily, what the operators were looking for was a level of control in managing their network which the network vendors couldn’t offer. The revolution burned the path that introduced open networking, and network disaggregation to the work of networking. Let us first learn about disaggregation followed by open networking.

  • Tracking Telco Progress in Open Networking
    I recently attended the Open Infrastructure Summit (formerly the OpenStack Summit -- more on this later). While the conference has gotten smaller, I didn't hear any complaints. Instead, people attending recognized that the developers who showed up came to work on real problems, rather than to cheerlead for the latest technology. Despite some of the dire headlines of the past year, I did not sense a crisis or panic.
  • Exclusive: Google suspends some business with Huawei after Trump blacklist
  • 5G and #Huawei – Trade wars can be prevented by using Open Source
    Consumer Choice Center Managing Director Fred Roeder stressed that more openness and transparency of telephone and radio networks could lead to more trust in the soft- and hardware of infrastructure providers: “Outright bans by country of origin should only be the last resort for policy makers. Bans risk getting the global economy deeper into costly trade wars. Consumers benefit from competition and the fast rollout of new technologies such as 5G networks. At the same time, we are worried about vulnerabilities and potential backdoors in equipment and software. Closed systems have a much higher likelihood of hiding vulnerabilities. Hence more open systems and open source approaches can really help consumers, and governments, trust the security promises of 5G providers,” said Roeder. “Private efforts such as the Open Radio Access Network Alliance show that open source systems are an option for telecommunication infrastructure. It would be a win-win situation for consumers and industry if more companies would embrace open standards. An open source approach in telecommunications could revolutionize market access and rollout pace of new standards in the era of 5G, in the same way as blockchain does in the financial services and payment industry. Manufacturers that commit to open source systems show that they don’t have any vulnerabilities to hide, and at the same time have a compelling case not to be excluded on the basis of their country of origin,” he added.
  • Why 5G is a huge future threat to privacy
    The next-generation of mobile communications, 5G, is currently a hot topic in two very different domains: technology – and politics. The latter is because of President Trump’s attempts to shut the Chinese telecoms giant Huawei out of Western procurement projects. That might work in the US, but the move is meeting a lot of resistance in Europe. There seem to be two primary concerns about allowing Chinese companies to build the new 5G infrastructure. One is a fear that it will help China consolidate its position as the leading nation in 5G technologies, and that it could come to be the dominant supplier of 5G hardware and software around the world. The other is more directly relevant to this blog: a worry that if Chinese companies install key elements of 5G systems, they will be able to spy on all the traffic passing through them. As the South China Morning Post reports, in an attempt to soothe those fears, Huawei has even promised to sign “no-spy agreements with governments“. That’s a rather ridiculous suggestion – as if signing an agreement would prevent Chinese intelligence agencies from using Huawei equipment for surveillance if they could.