Next-generation storeconfigs database for Puppet. Interestingly, still backed by a relational database but only PostgreSQL, not MySQL.

YAML-based CM tool.

Operations history lesson.

Puppet inventory management frontend and ENC.

Tool for quickly creating Debian metapackages. (Thanks, Hammond.)

Interesting shell-based configuration management tool.

Code drop (at time of bookmarking) of a monitoring system based on RabbitMQ specializing in monitoring ephemeral nodes.

(Dumping GitHub watches into Pinboard.)

Clojure-based declare-and-provision framework.

Gossip-based eventually-consistent (but for a small cluster likely always consistent) configuration storage engine like Noah.

Old-school source of truth for system configuration data.

"Don’t edit config files. Instead, edit the truth." There's some good stuff in here and yet a lot I disagree with. Decoupling "truth" from running systems I think is an abstraction for its own sake.

Interesting CM-focused analogue to Chubby/ZooKeeper/Doozer. I can't help but think the high-level API has muddled the design. I'd love to see that same API implemented in terms of Doozer.

Me at PyCon.

This HN thread (via Matt) lists a ton of problems I simply don't encounter. I'm not yet sure what that means for DevStructure, me, Puppet Labs, or the average Puppet user, but it's interesting to note.

A reasonably brief introduction to Puppet from the folks at Engine Yard.

Generic analogue to bits of Boto, Fog, Knife, et. al. Synchronous and inheritance-focused CM.

A Python-based configuration management system that focuses on automatically tracking config file changes. Seems like I could get most of the way to what this does with `while true; do git commit -am $(date); sleep 60; done`. The rest is file metadata tracking like etckeeper.

Dark-horse configuration management system.