The best part of using Progress Chef is that it doesn't depend on a single cloud infrastructure. We offer SaaS as well as Product as a Service. Given this, we provide infrastructure code and Docker images for applications to our customers. Therefore, we required a service that can manage both infrastructure code and application deployment, including the pipeline for future releases. In these terms, Progress Chef is the go-to solution for us, whether our customer is in AWS, Azure, or GCP.
What do you dislike about the product?
I would like it even more if I can get a managed service for using Progress Chef. The Infrastructure requirement for Progress Chef is a bit complex.
What problems is the product solving and how is that benefiting you?
The problems that are solved by Progress Chef are as follows:
1. It doesn't depend on cloud infrastructure. It can be used for AWS, Azure, GCP or On-Prem deployment as well.
2. Single software can be used for configuration management, CI/CD, IaC.
3. To deploy an entire application with infrastructure in a customer environment irrespective of the cloud provider they use, Progress Chef is the best solution available in the market.
Broad user community
ChefConf is an excellent conference
What do you dislike about the product?
It remains to be seen how Chef evolves after being acquired by Progress
The Chef technology itself for cookbook development has a not-insignificant learning curve due to how powerful it is
What problems is the product solving and how is that benefiting you?
Using Chef to automate configuration management allows DevOps teams to define policies that are repeatable, consistent and reusable. The result is increased business agility and security because all systems and resources are continuously and automatically evaluated, corrected, and modified.
I have used Chef in my previous company and have setup chef work station in my local. which was simple and it helps me to make some configuration changes without any downtime. it pulls configurations from the central server to the worker node
What do you dislike about the product?
Chef can improve their support community for better growth.
Initially, I have faced a few issue while writing the cookbooks it would have helped if they improve their support community.
What problems is the product solving and how is that benefiting you?
We have integrated chef with Jenkins which helped a lot . Also if we make some changes we used to fire one command chef-client which provides detailed reports and logs of the actions it performs during each Chef client run.
Progress chef is a great tool for Cloud Infrastructure Automation and Configuration Management
What do you like best about the product?
Progress chef is really easy in terms of Implementation. It has great number of features including Infrastructure Management, Release Automation, Task Management, Dashboard and Visualization etc
What do you dislike about the product?
Progress chef documentation can be made more simpler and adoptive. The quality if documentation is really important when it comes to implement a tool practically.
What problems is the product solving and how is that benefiting you?
We are using Progress chef for automating the Infrastructure deployment and Configuration tasks management.