It seems in the chef community lately there’s a growing trend for cookbooks to be kept in separate repos, or even separate branches in a single repo. I wanted to share the script I used to split out the community-cookbooks repo for Heavywater I knew the general git commands I needed to use, but it did take a few local trial runs to get it exactly as I wanted. To create the actual repos on github I made use of the excellent hub script. ...
One topic frequently tossed around at the recent Opscode summit was a re-org of the cookbooks repository. No more monolothic cookbooks repo on github, instead replaced by single cookbook repos, making it much easier to pull and contribute to a single cookbook. @jtimberman will be leading this effort. On a slightly unrelated note, it looks like @dysinger posted a handy little cleanup script:
The first historic Opscode Community Summit is officially over. See yesterdays post for a basic description of the event and structure. After another brief introduction, topics were discussed, a schedule arranged and the agenda was live. Topics for day two included: Managed Nodes a.k.a external entities Chef for big data projects, such as hadoop, cassandra and similar Ticket/triage process Network monitoring, it sucks Feature roadmaps, both short and long term ...
Opscode Summit day one has passed. I had to skip the sponsored dinner tonight, so for others it might still be going on. While there were lot’s of great sessions going on, and a great variety of people (seemed like 100+ in attendance), one thing stood out to me: The Chef community is awesome. To be fair, there are many great tech communities but the advantage the chef community has, and devops culture in general, is how many different skill sets are necessarily brought together combined with a culture of friendliness. Networking gurus, SysAdmin fanatics and passionate Devs are all brought together to solve some of the toughest challenges in modern computing infrastructures. ...