Chef Reviews

We use it for provisioning and ongoing configuration management. We provision boxes with Chef by taking a base AMI that already has Chef installed, and already has the appropriate credentials to connect to the main server. Then, this will be able to roll out and deploy the configuration. In addition, it runs every five minutes, so any unexpected changes to the configuration get automatically reverted. 

This means, you get developers, who go into the box and change something, thinking it will be okay. Then, they come to you, asking "Why isn't this change that I'm making working?" We have to explain, "Because it shouldn't be going into the box in the first place."

One thing that we've been able to do is a tiered permission model, allowing developers and their managers to perform their own operations in lower environments. This means a manager can go in and make changes to a whole environment, whereas a developer with less access may only be able to change individual components or be able to upgrade the version for software that they have control over. This allows us to return some of the control back to the developers, which saves our nights and weekends.

It's for deployment and configuration automation.

It streamlined our deployments and system configurations across the board rather than have us use multiple configurations or tools, basically a one stop shop. 

You set it and forget it. You don't have to worry about the reliability or the deviations from any of the other configurations.

Chef is like a master chef in a kitchen for computer systems. It's used to create recipes (cookbooks) that specify how servers and apps should be set up. Chef then makes sure these instructions are followed the same way on all computers in a network. The ChefServer is like the recipe book, where all these instructions are kept and shared, making it easier to manage and control how software and systems work in a company.

The most valuable feature is its easy configuration management, optimization abilities, complete infrastructure and application automation, and its superiority over other similar tools. It smoothly integrates with CI processes and helps reduce manual errors in system management and configuration. It is an effective and user-friendly tool for automating IT infrastructure and applications.

We use it for provisioning Adobe Experience Manager web application environments.

It has given us more resiliency in all the stuff we now manage with Chef, which was previously sort of manually maintained. Now, we are able to drive all of that through version control and automation, which is a lot faster.

Chef is primarily used for configuration management. For example, if you are managing a large number of servers (thousands or more), it is essential to ensure that the configurations across all servers are consistent. Otherwise, making any changes to the configurations would require writing a script to apply those changes across all the servers. Additionally, end-users may change configurations on multiple servers, leading to inconsistencies across different servers. To avoid this, configuration management is required.

We use Chef for this purpose by using a server-client mechanism. We apply changes to the Chef server, and every 30 to 40 minutes (depending on the configuration), Chef will verify whether the server has the required configuration. If not, it will revert to the required configuration automatically.

The solution could improve in managing role-based access. This would be helpful.

I used the solution to transform my infrastructure into code.

The solution is easy to use and learn, and it easily automates all the code and infrastructure. The solution quickly automates development in a cloud environment and provides flexibility for selecting multiple clouds in infrastructure. The solution is easy to use.

Chef is mostly for the operating systems to deploy or style, e.g. not containers. Before the containers, you need hardware, then an operating system, then you start to work on Kubernetes. To automate those steps, we use Chef.

The tool is useful for provisioning the operating system, because as you talk about the ops, sometimes customers ask to further deploy everything through automation, e.g. starting from scratch. You need to use different tools for you to provision via automation, so you need Chef. We use an automation tool such as Chef, then we were able to run Docker or containers on top of the hardware and operating system.

The features are good in Chef, especially its compliance feature. It's very good and it's what I found most valuable in the tool.

We use it for deployment of applications. It is a tool that you can use on the back-end for deploying architectures.

I have used the product for a couple years. I used to work for an online data center, and we used Chef for a lot of the tools and appointments.

When you are running a large cluster with hybrid applications, it can be very instrumental in making sure that they are running in sync. The tools it offers for running in environments has made it a good solution to use.