5 ms·
> Honest question; I've never understood why people have such a fixation on puppet-style tools. There are two things I want: 1. To describe the desired correc
by jacques_chester 14y ago
> Honest question; I've never understood why people have such a fixation on puppet-style tools.
There are two things I want:
1. To describe the desired correct configuration as a directed, acyclic graph.
2. To have some automatic compare-and-repair mechanism regularly bring my systems to such a state.
If you don't have a good tool for those two requirements, you wind up reinventing it anyway.
Your small shell scripts start being littered with lots of checks for this and that file, if-thens and cases. Then they break when script 27 silently gets out of sync with script 42.
You realise one day that system configurations can be expressed as DAGs (possibly it's a new insight, perhaps you were reading ITIL documentation). And you begin to dream about a tool that can take a descriptive DAG and generate the correct shell scripts. You have now half reinvented puppet.
But the systems still get out of sync. So you start tinkering with a tool that periodically checks each system and reruns the correct script. Now you have to ensure that your scripts are all idempotent. All those if-thens and checks creep back in.
So now you begin to dream about a system that only generates the steps needed to close the gap between the DAG and the current state of the system.
Congratulations. You just reinvented the other half of puppet.
- contingencies 14y ago> 1. To describe the desired correct configuration as a directed, acyclic graph. If you have already decided on your solution before you have analyzed the problem then there's nothing to discuss. > 2. To have some automatic compare-and-repair mechanism regularly bring my systems to such a state. Right. My fundamental point is that puppet-esque solutions only describe certain aspects of the system state, ultimately failing here and resulting in 'configuration drift'. Entire system images are far more elegant. Most of the use cases I have seen for puppet-style stuff are legacy-situation based and only make sense within that context. So what is the alternative to puppet-style solutions? Personally I use full system images on cloud and cluster solutions (corosync/pacemaker) to maintain server state.
- jacques_chester 14y ago> If you have already decided on your solution before you have analyzed the problem then there's nothing to discuss. You can see how I arrived at that solution. > My fundamental point is that puppet-esque solutions only describe certain aspects of the system state, ultimately failing here and resulting in 'configuration drift'. Particularly with runtime / process supervision. One of my pet peeves. > Entire system images are far more elegant. Yes and no. It really depends on what your cost/benefit tradeoffs are. I like system images for startup, but systems still drift from their initial configuration no matter how that configuration is established (DAG or blob). Even with system images you'll need to detect divergence from ... what, exactly? Doing a byte-for-byte comparison is going to suck. Do you just kill and relaunch periodically? I can see that being stochastically effective.
- contingencies 14y ago> Do you just kill and relaunch periodically? I can see that being stochastically effective. Personally no, but you easily could. > It really depends on what your cost/benefit tradeoffs are. Well, realistically, to facilitate automated deployment and testing of multi-machine systems you really do need to be operating at this level of abstraction. (ie. to declare your desired state). Once you reach this point, a configuration file for some version of a package within some node is really a distraction rather than a help; it should have been abstracted to some known-good state and taken out of the equation if you are to have any hope of staying sane. Many people use entire system images coupled with service monitoring as the de-facto segregation point for management purposes. > Do you just kill and relaunch periodically? I can see that being stochastically effective. While that's entirely possible and probably a reasonable approach in some cases, the corosync/pacemaker de-facto/spiritual approach is to detect issues with a given resource (roughly: 'service instance'), automatically destroy it and fail over to another instance thereof, and then potentially start another instance to replace it automatically on the same, or some other cluster node. To facilitate rapid failover, the master/slave paradigm allows you to have live backup nodes running and promote them as masters easily. Any type of hardware or software can be scripted as a managed resource. The type and frequency of resource health monitoring checks can be custom defined.