TrustRadius
Chef is IT workload automation software from the company of the same name (formerly Opscode) in Seattle, Washington.https://dudodiprj2sv7.cloudfront.net/product-logos/S2/8n/T70VQ0BGK1KH.JPEGChef SoftwareGet Cookin with Chef2018-11-28T17:09:16.382ZChef is a tool that is being used as part of a DevOps enablement movement that we are implementing throughout our business unit, and hopefully our organization in the future. It will help automate the manual task of creating and configuring new servers, testing existing servers for compliance regulations, as well as providing on-going maintenance for our infrastructure.,Chef is very easy to learn. Written in ruby, Chef code is high enough level for non-ruby coders to get a general idea of what the script is doing.
Chef can be a one stop shop for writing code, testing infrastructure, and deployment of applications.
The Chef support team is very helpful in their auto manager support as well as active support in their Slack channels from development engineers & architects.,Chef could do a better job with integration with other DevOps tools. Our company relies on Jenkins and Ansible, which took some development and convincing for plug-ins to be created/available.
It would be nice if kitchen didn't only have a vagrant/virtual-box prerequisite. Our company one day stop allowing virtual-box to run without special privileges, and that caused a lot of issues for people trying to do kitchen tests.
Chef could use more practice materials for the advanced certification badges. There was not a lot of guidance in what to study or examples of certain topics.,9,Able to reduce the numbers of hour a particular team would take for server maintain and deployment.
Implementing Chef requires a change in paradigm for teams that are not open to the DevOps lifestyle. Half of the teams where Chef was introduced reverted backed to their old manual ways of doing things.
Our timeline for code deployment went from once every two to three months, to about 1 month, then eventually once every 2 week sprint.,Ansible and Puppet Enterprise (formerly Puppet Data Center Automation),Bitbucket, Jenkins, Logstash, Splunk Enterprise, DatadogVerified UserCentralized Configuration Management2018-03-02T22:55:22.702ZChef is a great technology for centralized configuration management. Therefore it's perfect for configuring complex, interconnected systems where parameters may be shared, or facts (e.g. ip address,..etc) about other nodes are needed to populate configuration files. Chef provides advanced capabilities such as encrypted data bags (to store configuration variables), versioning, roles, cookbooks repositories,..etc. It's very advanced and great system for managing large and complex clusters.,Centralized Configuration Management; Chef really excels at that as it provides a wide range of features that are well thought of, such as data bags, encrypted data bags, roles, shared repositories, cookbooks versioning, environment locking..etc
Chef is based on Ruby and therefore it has all the capabilities of this powerful scripting language, unlike other tools that has its own DSL. This means greater flexibility to implement really custom logic.
Chef community has made an impressive progress with regards to automated testing of cookbooks.,Chef complexity sometimes backfires when managing large clusters. Since a node can have different sources for variables, it can easily get messy and hard to troubleshoot.,9,Any configuration management when done correctly will have a significant ROI. Chef in particular is great because the architecture, the language syntax and design is very innovative.,Ansible, Puppet Data Center Automation and Docker,Docker, Puppet Data Center Automation, AnsibleAiman NajjarChef review2018-05-17T16:30:31.801ZUsed as the infrastructure-as-code tool for everything that we use.,Unit testing
Integration testing
Deployments,Agent-less
Push type jobs support,10,Lower downtime
Increased time to market by a factor,Ansible,JIRA Software, TeamCityPavel JeloudovskiChef for IaC and reliable deployments2018-07-09T09:46:51.101ZWe use multiple Chef servers. We had 2 Chef servers hosted in our Business Unit, one for production and another for pre-production. We developed on that and maintained them too. Apart from these 2 we have organizational wide Chef servers which can be used by any BU and a central tools team maintains those servers. We are using Chef not only for IaC but also for deployment purposes.,Chef helps maintain all the servers of one logical group to be in the same state. This helps in maintaining a standard across all the servers.
Concepts in Chef like roles, environments and tags helps a lot in logical grouping and executing corresponding cookbooks on them to maintain the stability.
We use Chef not only for infrastructure as code but also for reliable deployments.,One main concern with Chef is the maintainability of Chef master.
The Chef-client should be installed on every node we want to do any automation.
It is mostly Ruby and there's a learning curve. Need to understand the fundamentals of Chef very throughly to play around with attributes, templates etc etc.
The Chef-client agent needs to be run on the nodes frequently to update the details of it state to master. And also to index the nodes based on tags.,8,Chef is a good tool for baselining servers. It will be a good ROI when there are huge number of servers. For less number of servers maintaining a master will be an over head.
One good ROI will be that the Operations Team also gets into agile and DevOps methodologies. Operational teams can start writing scripts/automations to keep their infra more stable and their application stack more reliable.
Implementation of Chef eliminates the manual mode of doing things and everyone aligns to automation mind set. It helps in change of culture.,Ansible,GitHub, Jenkins, AWS OpsWorksVerified UserChef @ SAP2018-02-06T17:18:59.308ZChef is used as a middleware for our private managed cloud software. Chef is used in an in-house utility called Arc, that installs a Chef-agent in each server that users spin up, and then run all the cookbooks that are in the run list.
The business problems [it addresses] are: tidy up servers, control the diverse apps versions, generate a catalogue of apps and configs for the company's usage.,Attributes in files can be changed once, instead of walking all over the recipes.
Ohai - generates machine parameters non-stop.
Databags keep some more secured information for usage with the recipes.,Chef, unlike Ansible, must use its own agent. Ansible just uses the "already" pre pared "SSH" utility.
Engine run time - need to speed up the time for cookbooks run, like in ZEROMQ of SALTSTACK.,9,AD - active directory connection, which was done with Ohai and was a super generic cookbook that was marvelous and reduced all the setups in each server.
Amazing time-saving cookbook.,Ansible and Docker,Jenkins, JIRA SoftwareOfir Gutmacher
Unspecified
Chef
31 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow'>trScore algorithm: Learn more.</a>
