Chef PAYG
Progress Software CorporationExternal reviews
89 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Amazing tool to maintain large IT infrastructure
What do you like best about the product?
The biggest upside is the ability to maintain IT infrastructure config as code. This allows for easy scaling and management of resources. It also ensures no unplanned configuration drift.
What do you dislike about the product?
The minor inconvenience with using chef is handling the installation of the chef client on the remote hosts.
I think it would be better if chef provides an easier tooling to manage the initial setup/installation of the chef-client on the hosts.
I think it would be better if chef provides an easier tooling to manage the initial setup/installation of the chef-client on the hosts.
What problems is the product solving and how is that benefiting you?
The biggest advantage of using chef is the ability to manage configuration as code, that is the biggest advantage for us.
DevSecOps via code
What do you like best about the product?
I like the fact that you can control your Operations via code. This allows you create a server repeatedly with changes can be made with very little effort.
What do you dislike about the product?
To get to good DevSecOps a lot of code needs to be written.
What problems is the product solving and how is that benefiting you?
I would like to see Progress create more methods that create a hardened box without much coding.
Save time with Chef
What do you like best about the product?
Progress Chef allows our developers to have more control over their web application infrastructure, thereby allowing the developers to roll out web applications and services more quickly.
What do you dislike about the product?
- Figuring out the syntax required in Ruby to implement a given resource update is sometimes difficult.
- It's not easy to pass status information from powershell scripts back to Chef/Ruby.
- It's not real clear what Progress Chef is responsible for vs the Chef community.
- It's not easy to pass status information from powershell scripts back to Chef/Ruby.
- It's not real clear what Progress Chef is responsible for vs the Chef community.
What problems is the product solving and how is that benefiting you?
Progress Chef automates a lot of the IIS setup that we previously performed manually. That speeds things up for our developers, as they don't have to submit service requests to IT Infrastructure to configure IIS. We are also now making additional use of Chef Inspec to ensure that our servers are hardened to CIS level 1 requirements.
Its good tool for pull model for both windows and Linux nodes
What do you like best about the product?
We like to use this for push model for CIS benchmark configurations
What do you dislike about the product?
It is good if we can have push model to use to deploy configurations.
What problems is the product solving and how is that benefiting you?
It resolves most of the configuration keys in CIS benchmark model
Chef opened the door for working with new technologies
What do you like best about the product?
Good toolset, good docs, support & community.
Complete solution with useful features.
Is in constant development using feedback from customers.
Great to work with from a developer standpoint.
Complete solution with useful features.
Is in constant development using feedback from customers.
Great to work with from a developer standpoint.
What do you dislike about the product?
Bumpy or scattered product roadmap; eg. policyfiles introduced as an afterthought, and this also shows in the web UIs. Chef Automate UI not my personal favourite.
What problems is the product solving and how is that benefiting you?
Testing new developments on local machines,
Installing required toolsets for newly provisioned servers,
Having general overview of automation runs,
Being able to roll out updates to great number of servers at once
Installing required toolsets for newly provisioned servers,
Having general overview of automation runs,
Being able to roll out updates to great number of servers at once
Chef Review
What do you like best about the product?
Chef is really powerful configuration management tool with great customization options and flexibility.
What do you dislike about the product?
Agent installation, complexity of use and troubleshooting steps
What problems is the product solving and how is that benefiting you?
Robust configuration management
Chef is a great product, but I have some concerns.
What do you like best about the product?
Chef is a great product, and it solves many of the problems we have with compliance and policy enforcement. We have reasonably good support from our success team.
What do you dislike about the product?
Development on the product seems hit or miss, sometimes rushed and not always well documented. Sometimes our customer success resources aren't sure how to solve our problems. It seems evident that something has happened internally to Progress/Chef, which is impacting their ability to develop and release stable products. This is a little panic-inducing for a company using Chef across an install base of nearly 70,000 servers.
What problems is the product solving and how is that benefiting you?
As mentioned, we solve quite a few build, deployment and compliance problems with Chef. Much of that work is purely steady-state, not actively developed or changed. We're hoping new versions of Chef client, Chef Automate and the underlying technologies can start driving more progress and involvement in developing Chef.
unlocking knowledge to next level to benefit personal skills
What do you like best about the product?
Overall sessions are good; thank you for an excellent course.
What do you dislike about the product?
nothing, Quality of the content was excellent.
What problems is the product solving and how is that benefiting you?
building database automation
Great tool for managing packages, softwares and scripts on multiple systems
What do you like best about the product?
Formerly known as CHEF, it is used to manage all the slave systems, so we don't have to manually log in to each of the slave nodes or machines to be able to install software systems.
I used it when I was working in one of the previous product organization. We used CHEF to install multiple dependencies on the system by defining a cookbook and recipe.
So basically we can define a set of tasks which has to be executed on the system and CHEF automatically logs in to the system and does the software install, package install or maybe change the configuration.
In the big data world, suppose a node is required to have the software needed before it can operate. we just can run chef-client and it does everything automatically.
This is an amazing tool and works fast without any hassles.
I used it when I was working in one of the previous product organization. We used CHEF to install multiple dependencies on the system by defining a cookbook and recipe.
So basically we can define a set of tasks which has to be executed on the system and CHEF automatically logs in to the system and does the software install, package install or maybe change the configuration.
In the big data world, suppose a node is required to have the software needed before it can operate. we just can run chef-client and it does everything automatically.
This is an amazing tool and works fast without any hassles.
What do you dislike about the product?
Since it is built on top of ruby, sometimes it's hard to figure out what has caused the error.
There have been instances where the chef-client has failed, and it was pointed to an error, and late we got to know that it is related to ruby installation.
sometimes, the chef errors are hard to debug. There is no intelligent troubleshoot mechanism and does not suggest user where to look for exact errors and fixes.
There have been instances where the chef-client has failed, and it was pointed to an error, and late we got to know that it is related to ruby installation.
sometimes, the chef errors are hard to debug. There is no intelligent troubleshoot mechanism and does not suggest user where to look for exact errors and fixes.
What problems is the product solving and how is that benefiting you?
Mainly we used it to manage different nodes or the machine in the cluster.
Since we used to work on the big data problem, and big data requires lots of nodes, and if one node fails, we have to reinstall all the software and packages required - also creating a custom folder, installing java, python etc.
Installing it on let's say 50 systems one by one is not feasible and would kill lot of time, so CHEF comes handly. we can define cookbook and recipe and execute the chef-client in the slave systems, and all the software and packages get installed automatically.
Since we used to work on the big data problem, and big data requires lots of nodes, and if one node fails, we have to reinstall all the software and packages required - also creating a custom folder, installing java, python etc.
Installing it on let's say 50 systems one by one is not feasible and would kill lot of time, so CHEF comes handly. we can define cookbook and recipe and execute the chef-client in the slave systems, and all the software and packages get installed automatically.
Chef for cooking safe security
What do you like best about the product?
I like the open community with lots of resources present in the documentation and also video tutorials which help someone like me who was new to this technology pick up and complete the tasks assigned easily and effectively .
What do you dislike about the product?
Compatibility with different programming languages such as python.
What problems is the product solving and how is that benefiting you?
Benchmarking and compliance is a huge headache for anyone working in this sector which is minimized by chef.
showing 31 - 40