<div dir="ltr">Pull vs push is always one of those important arguments that leans heavily on a teams political organization and coupling between server roles.<div><br></div><div>Much "site wide" stuff and even per node stuff can be factored off the local box and into shared network resources like LDAP, DNS, NFS, and the like.<br></div><div>With total control of the nodes the need for per-system customization via a CM tool is minimized. Much of the time a good network boot script and a 'dpkg --get-selections' file can go a long way to getting the server complex up and running and properly customized with the right bits. System drift can be corrected by rebuilding it.</div><div><br></div><div>With this kind of organization then there are typically only a few files or services that you might want to manage directly on nodes. A very simple CM system will meet that need.</div><div><br></div><div>chris</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Mar 25, 2016 at 12:53 PM, David L. Anselmi <span dir="ltr"><<a href="mailto:anselmi@anselmi.us" target="_blank">anselmi@anselmi.us</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">Chris Fedde wrote:<br>
> I'm always surprised that rdist never comes up in this discussion. That was<br>
> the system we used at the old USWest and I brought it with me several other<br>
> places. Having spent a year each with cfengine, puppet and ansible I'm<br>
> retuning to rdist at my next opportunity.<br>
<br>
</span>You should give a talk on how you used rdist and how it was better than the others. I'd come if it<br>
wasn't on a Saturday.<br>
<br>
I think I used rdist long ago. It pushes files out to remote machines, right?<br>
<br>
So the obvious disadvantages of that seems to be that it's reuse by cut and paste and it either<br>
bypasses your package manager or you build package stuff on top of it. But maybe you have better<br>
experience than I.<br>
<br>
I don't think it would be any worse than what I'm contemplating for bootstrapping, though<br>
debootstrap already connects that to package management. I'll eventually have to see if there are<br>
<br>
One thing I'd like to see, though I don't know whether anyone is doing it, is that machines manage<br>
themselves. So they get a config and apply it, rather than some other machine making changes to<br>
them. That may not matter much in practice, and it may not be as available as I hope. But I'm<br>
guessing rdist doesn't work that way (it didn't when I used it last).<br>
<div class="HOEnZb"><div class="h5"><br>
Dave<br>
_______________________________________________<br>
clue mailing list: <a href="mailto:clue@cluedenver.org">clue@cluedenver.org</a><br>
For information, account preferences, or to unsubscribe see:<br>
<a href="http://cluedenver.org/mailman/listinfo/clue" rel="noreferrer" target="_blank">http://cluedenver.org/mailman/listinfo/clue</a><br>
</div></div></blockquote></div><br></div>