Chris's Wiki :: blog/sysadmin/ConfigMgmtSetupTradeoffs Commentshttps://utcc.utoronto.ca/~cks/space/blog/sysadmin/ConfigMgmtSetupTradeoffs?atomcommentsDWiki2013-09-27T14:19:50ZRecent comments in Chris's Wiki :: blog/sysadmin/ConfigMgmtSetupTradeoffs.By MikeP on /blog/sysadmin/ConfigMgmtSetupTradeoffstag:CSpace:blog/sysadmin/ConfigMgmtSetupTradeoffs:e5962ff98cd500430ba993fdacc3d6402bb5cbfeMikePhttp://snowcrash.ca<div class="wikitext"><p>"Here I want to mention that we're unlikely to consider it a feature that a core component of our build instructions keeps evolving rapidly on us."</p>
<p>Yes. The CM advocates say it's required; I say that's fine if your job is to install new systems, not so fine if your job is to use the systems you're doing the installs on.</p>
<p>When you're spending non-trivial effort to maintain the tools that are supposed to help you maintain the tools, you've got a problem if what you're interested in is... well, anything but maintaining configuration management systems.</p>
</div>2013-09-27T14:19:50ZBy Christian Neukirchen on /blog/sysadmin/ConfigMgmtSetupTradeoffstag:CSpace:blog/sysadmin/ConfigMgmtSetupTradeoffs:79f9e1dcc6216e5d0857752cac395ee6eb5d7234Christian Neukirchenhttp://chneukirchen.org/<div class="wikitext"><p>IMO, the only initial dependency should be a running sshd and some kind of shell (even bash if it has to be). I could imagine also having a dependency on <em>some</em> version of Python and shipping around the actual code over the SSH session, like "sshuttle".</p>
<p>Of course, the CMS can update itself then, after bootstrapping.</p>
</div>2013-09-26T13:33:54Z