Please add a link to the community cookbook site to the chef web UI.
I admit I’m a beginner… I’m using a self-hosted chef on a Virtual Box to practice, and Hosted Chef for the one, two, three machines I’m currently taking care of.
An opscode hosted CI for community cookbooks
With growing number of community cookbooks and available testing frameworks for chef, it will be helpful if the community cookbooks go through a CI (something like travis) where the cookbooks are tested against their supported operating systems. The end result should be the build status for individual cookbooks available in the community site along side their version compatibly with their dependent cookbooks (something that gemnasium provides for ruby gems). It will greatly facilitate development of portable less buggy cookbooks available in community.
Multiple pem files per user.
I would like to be able to have different keys for different organisations. ie at work I would use my work key, but at for my private infrastructure I would use another key. Similar to how GitHub does it, allowing you to register multiple keys per user. In GitHub’s case, the keys do not have to be tied to a particular organisation.
Make chef-server, chef-solo, and chef-client easier to install
I could not get chef-server installed on my CentOS server using any of the info from your wiki. After 2 days of trying i finally gave up and had to go to a 3rd party rpm. From there I had chef server installed in about 15 minutes.
If some guy on some website can make it that easy why can’t you guys? Doesn’t have to be an rpm. It could be a bootstrap cookbook or a script. I know your project is more oriented towards ubuntu but I much prefer to work with CentOS and so do a lot of other people.
I did manage to get your chef-client bootstrap procedure working but even that was much more difficult than I believe it needs to be.
Please make chef-client more light weight.
Currently this is a show stopper for me. Chef-client puts too much load on my servers and uses too much memory. So what I am doing for now is only running the service manually and then shutting it down when not in use. Obviously this is less than ideal as you scale up and kind of defeats the purpose of chef in the first place.