Configuration systems have historically looked at config as bits-on-a-disk.
Supervisor systems look at bits-in-memory.
And they emerged and evolved independently. So there's pain points and impedance mismatches regardless of which one you start with.
What's needed is a system that sees that configuration and supervision are the same problem: you have a directed graph of what a system can look like, plus a compare-and-repair mechanism to drag the system to that state frequently.
I've personally looked at Chef, Puppet and Cfengine, none of which really does all of them the way I would like.
Configuration systems have historically looked at config as bits-on-a-disk.
Supervisor systems look at bits-in-memory.
And they emerged and evolved independently. So there's pain points and impedance mismatches regardless of which one you start with.
What's needed is a system that sees that configuration and supervision are the same problem: you have a directed graph of what a system can look like, plus a compare-and-repair mechanism to drag the system to that state frequently.
I've personally looked at Chef, Puppet and Cfengine, none of which really does all of them the way I would like.
http://chester.id.au/2012/06/27/a-not-sobrief-aside-on-reign...