15 ms·
Honest question; I've never understood why people have such a fixation on puppet-style tools. Small-scale? Run a simple script. Large-scale? Use a network-host
by contingencies 14y ago
Honest question; I've never understood why people have such a fixation on puppet-style tools.
Small-scale? Run a simple script.
Large-scale? Use a network-hosted configuration (optimally read-only root and network booting so the entire system is known-good) to avoid the entire class of configuration drift / migration / state-accrual problems associated with the above.
I just see puppet as sort of trying to provide the latter and failing, resulting in a complex version of the former.
- dschep 14y agoHow do you propose implementing a netbooted infrastructure with laptops?
- contingencies 14y agoIf they are always on the network, it's trivial, you just boot from the network as with any other machine. If they are often on the network, you can use occasional rsync, for example to the system partition either at boot or in the background. That way, boot is possible even if disconnected. If they're not often on the network, and you are seriously considering doing this at all, I would reconsider which problem you are trying to solve. Also: I don't know about anyone else here, but I would prefer not having a company manage my laptop. The use cases for such a scenario, in my view, are pretty hard to imagine.
- mpdehaan2 14y agoThis kind of feeling is a large reason why I created http://ansible.cc/ http://ansible.cc/ The feeling that I want to write something quick or easy shouldn't depend on the size of my infrastructure, it should be easy either way -- 500 servers, 50, 1, doesn't matter. That being said, our modules do need some patch-love for things like launchd and OS X groups, we've been a lot more Linux/Unix focused to date. (Patches are welcome of course!)
- contingencies 14y agoThanks for your reply Michael. I had a look at Ansible and your personal website and you definitely have been doing work with a fair bunch of serious systems in this space, so I really value your perspective. However, looking at the ansible news and documentation - "playbooks, configuration management, deployment, and orchestration" - I really couldn't see how it differs significantly in paradigm to puppet. Is it just the ability to converge on some defined configuration automatically? It's unclear to me. Would you be so kind as to summarise the differences in brief? Thanks.
- mpdehaan2 14y agoSure, multi-tier has been a focus from day 1, so a common example is a workflow where you want to hop between tiers of a 3-tier application, touch load balancers and monitoring along the way, and so on... that's all trivially possible primarily because it's push, not pull, based. Ansible can both code up and execute those kinds of workflows very quickly. A major core other aspect is not requiring any agents on the remote nodes, not even having a server, and not needing an additional PKI. Because it's using SSH, it's using your OS credentials, so if your boxes are, for example, using Kerberized SSH, that just works out of the box. The resource model is still very puppet-like (state=absent/present, idempotence, etc), in that we have states and convergence, but I have tried in many places to not make this a programming language, and keep the amount of syntax down. A key focus was making the content readable, so you didn't have to think about dependency ordering and could tell by skimming the playbooks top to bottom exactly what they will do.
- 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.
- parasubvert 14y agoNetwork hosted configurations are the scourge of most admin's existence due to the emphasis it places on network reliability and performance along with a SPOF for the network storage. The other aspect is that many admins are ally do not like the bad habits associated with an image-level of abstraction, which leads to many hidden dependencies and configurations settings. Aa package-level manifest like Puppet, Chef, or Ansible enables much more of a complete explicit specification of the environment along with cross-machine dependencies. Such a description also allows easier reassembly of subsets of the system into different combinations. The trend towards image-level abstractions does work for many as an alternative: Netflix for example avoids Puppet and just reassembles AMI images on each deploy, with auto discovery of cross machine dependencies at runtime via (eg) Zookeeper or other cluster facilities. But they have the discipline not to get into an image sprawl situation.