CFEngine: Here I come to get my hands dirty

So I have been learning CFEngine quite a while now. Being a Puppet guy, it was scary at first. I thought I would get lost in “Bundle”, “Body”, “promise”, “repair” and so on.

But, as always, the best way to learn a new technology (by the way CFEngine is the oldest of all config management tools) is to setup a home lab and try as many dirty things as you can. The more I am learning CFEngine, the greater the respect I feel towards it. It’s awesome and believe me or not: It’s really really simple to write a CFEngine policy, no harder than writing a Puppet manifest.

So wanted to share the policies I wrote for my home lab, including the interesting one: defining a cluster and pushing configs as per the cluster definition.

Checkout my github repo:

Many more to come as I explore more and more.



About admin_xor

Un*x/Linux junkie, loves to program, automate, automate and automate
This entry was posted in Cfengine and tagged , , , . Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s