We contributed a lot of work to the latest Chef release, which made it out over the weekend. Most notably we got a lot of FreeBSD support in, and it looks like a few people are going to give that shot. The release notes are the best source of information about what was added. As we’re moving puppet recipes over to chef we stumble across pieces of configuration that we’d rather be a resource, and try to add that support. We’re really excited about what we’re getting into Ohai. I tested support that Ben Black is working on for reading libvirt data through their ruby API, and it’s just going to be awesome. With puppet+iclassify I had some convoluted ways of getting guest information, but this implementation is going to be first class enterprise stuff.
Recent Posts
- Stubbing class constants with rspec and Ruby
- Downloading All The Github Repositories
- Generating entropy in the cloud
- Disabling Firefox shortcuts on OS X
- Recreating the Opscode Chef validation key
- require-rubygems.overrides and gem2deb 0.2.2
- locale errors on debian
- Creating a Debian sid emi for Eucalyptus
- LVM errors with sbuild
- munin-cgi-graph with fcgid on ubuntu lucid
Archives
What I'm Doing...
- @tomasczt dude, did you see that commercial? Broderick? Brodercik? in reply to tomasczt 8 hrs ago
- @cemerick source dependencies? -- Each cookbook must list its dependencies in its metadata. Knife can/will walk these for you. in reply to cemerick 10 hrs ago
- @cemerick @opscode I'm not familiar with Pallet. Commenters do not sound familiar with current versions of Chef or common knife workflows. in reply to cemerick 11 hrs ago
- More updates...
Posting tweet...
Powered by Twitter Tools