Chef SaaS
Progress ChefReviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
83 reviews
from
External reviews are not included in the AWS star rating for the product.
Great tool for system configuration management
What do you like best about the product?
Chef is pretty solid for configuration management of Windows machines and ensuring that they are all setup and provisioned the same way. The setup and scripting of recipes is pretty extensive, and Windows support is solid. There are a variety of recipes to do most windows configuration needed, as well as Linux.
What do you dislike about the product?
The setup is pretty complex, it can take awhile to just setup a server and figure out how to connect a client to it. It would be nice to have more functionality exposed in the Chef GUI, using command line for a majority of tasks can be tedious at times. Chef is mainly geared toward ensuring a server is configured properly, but it would be nice to have the option for 'one off' tasks. When you have agents already running on your systems for Chef it would be nice to run a task on a subset of machines instead of yet another agent and management system for that. It also runs best if you have a person dedicated to the configuration and on going maintenance of Chef. It takes some effort to keep up on your recipes.
What problems is the product solving and how is that benefiting you?
Chef solves the system configuration management issue pretty well, it is able to ensure that machines are setup similarly. The 'configuration as code' aspect makes it clear to the organization what is involved in setting up and configuration of a server. It helps to document the process as long as you follow through on continuously adding recipes as you move along.
Recommendations to others considering the product:
If you are using Azure, check out Microsoft's Azure lab on setting up Chef, it significantly speeds up the implementation process. Be sure to run through some tutorials and documentation on the Chef website as it is very difficult to setup straight out of the box. There aren't really any wizards or in-product tutorials.
Chef is Awesome!
What do you like best about the product?
The shear amount that you can do with the product from Linux to Windows, configurations to application deployments, Chef is delightfully AWESOME!!!!!
What do you dislike about the product?
I personally don't have any dislikes for Chef as a product. The only caveat is when creating resources, you'll need to increase your Ruby knowledge and skills.
What problems is the product solving and how is that benefiting you?
When I jumped on the infrastructure as code bandwagon, I was testing both Chef and Puppet to Linux and Windows deployments. I chose Chef as they fixed a pending reboot issue with RDSH first. As a Solution/managed Service provider, the ability to reduce deployment time with a standard automated deployment methodology is invaluable.
Recommendations to others considering the product:
To learn Chef, I highly recommend using the http://learn.chef.io . Even for an OPs guy, Chef is awesome!
Chef is Infraestructure as a Code
What do you like best about the product?
Not biased to said that everything from Opscode - Chef was well design, from their solo version to the Chef Provisioning module. You can write and deploy your whole infraestructure.
What do you dislike about the product?
Chef Server Operation could give trouble as in performance issues.
What problems is the product solving and how is that benefiting you?
Infraestructure as Code. Continuos Delivering and Integration.
Recommendations to others considering the product:
Design well and do not forget to have clever metrics from your CI and CD workflow
showing 81 - 83