CFEngine best practices: part 2
Continuing on from testing best practices, let's look at other best practices to make you a CFEngine ninja.
CFEngine best practices: testing
CFEngine's autonomous automation means that your policy, mistakes and all, will be duplicated quickly to all of your hosts. --- Potentially tens of thousands of them. When I taught martial arts it was humbling to watch a class of thirty duplicate my incorrect movement. I didn't know, because I didn't test myself. In martial arts I was simply embarrassed, but in configuration management, mistakes could cost me a raise or even my job. Testing is the paramount best practice for CFEngine. Let me tell you what I have learned.
Predict the future with Delta Reporting and CFEngine
Until now Delta Reporting was only able to show you the outcome history of all your promises. Now it can show you the future.
Continue reading Predict the future with Delta Reporting and CFEngine...
Class definition with CFEngine 3.6 and JSON
JSON in CFEngine 3.6, coming soon, offers a great way to separate your data from your policy. Consider this example. It sets the promiser class if the host's unqualified hostname is found in the hosts list. If you want add or remove hosts or classes, just edit the JSON file. Look for this in EFL after CFEngine's 3.6 release.
Continue reading Class definition with CFEngine 3.6 and JSON...
Delta Reporting answers questions about your CFEngine infrastructure
Learn what Delta Reporting can answer for you, all from one place.
Continue reading Delta Reporting answers questions about your CFEngine infrastructure...