www.nico.schottelius.org/software/cdist/man/4.3.2/cdist-why.html
2016-10-13 18:54:46 +02:00

299 lines
No EOL
11 KiB
HTML

<!DOCTYPE html>
<!--[if IE 8]><html class="no-js lt-ie9" lang="en" > <![endif]-->
<!--[if gt IE 8]><!--> <html class="no-js" lang="en" > <!--<![endif]-->
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>2. Why should I use cdist? &mdash; cdist 4.3.2 documentation</title>
<link rel="stylesheet" href="_static/css/theme.css" type="text/css" />
<link rel="index" title="Index"
href="genindex.html"/>
<link rel="search" title="Search" href="search.html"/>
<link rel="top" title="cdist 4.3.2 documentation" href="index.html"/>
<link rel="next" title="3. Supported Operating Systems" href="cdist-os.html"/>
<link rel="prev" title="1. cdist - usable configuration management" href="cdist-intro.html"/>
<script src="_static/js/modernizr.min.js"></script>
</head>
<body class="wy-body-for-nav" role="document">
<div class="wy-grid-for-nav">
<nav data-toggle="wy-nav-shift" class="wy-nav-side">
<div class="wy-side-scroll">
<div class="wy-side-nav-search">
<a href="index.html" class="icon icon-home"> cdist
</a>
<div class="version">
4.3.2
</div>
<div role="search">
<form id="rtd-search-form" class="wy-form" action="search.html" method="get">
<input type="text" name="q" placeholder="Search docs" />
<input type="hidden" name="check_keywords" value="yes" />
<input type="hidden" name="area" value="default" />
</form>
</div>
</div>
<div class="wy-menu wy-menu-vertical" data-spy="affix" role="navigation" aria-label="main navigation">
<ul class="current">
<li class="toctree-l1"><a class="reference internal" href="cdist-intro.html">1. cdist - usable configuration management</a></li>
<li class="toctree-l1 current"><a class="current reference internal" href="#">2. Why should I use cdist?</a><ul>
<li class="toctree-l2"><a class="reference internal" href="#known-language">2.1. Known language</a></li>
<li class="toctree-l2"><a class="reference internal" href="#powerful-language">2.2. Powerful language</a></li>
<li class="toctree-l2"><a class="reference internal" href="#more-than-shell-scripting">2.3. More than shell scripting</a></li>
<li class="toctree-l2"><a class="reference internal" href="#zero-dependency-configuration-management">2.4. Zero dependency configuration management</a></li>
<li class="toctree-l2"><a class="reference internal" href="#push-based-distribution">2.5. Push based distribution</a></li>
<li class="toctree-l2"><a class="reference internal" href="#highly-scalable">2.6. Highly scalable</a></li>
</ul>
</li>
<li class="toctree-l1"><a class="reference internal" href="cdist-os.html">3. Supported Operating Systems</a></li>
<li class="toctree-l1"><a class="reference internal" href="cdist-install.html">4. How to install cdist</a></li>
<li class="toctree-l1"><a class="reference internal" href="cdist-update.html">5. How to update cdist</a></li>
<li class="toctree-l1"><a class="reference internal" href="cdist-support.html">6. Support</a></li>
<li class="toctree-l1"><a class="reference internal" href="cdist-features.html">7. Features</a></li>
<li class="toctree-l1"><a class="reference internal" href="cdist-quickstart.html">8. Quickstart</a></li>
<li class="toctree-l1"><a class="reference internal" href="man1/cdist.html">9. cdist(1)</a></li>
<li class="toctree-l1"><a class="reference internal" href="cdist-bootstrap.html">10. Bootstrap</a></li>
<li class="toctree-l1"><a class="reference internal" href="cdist-manifest.html">11. Manifest</a></li>
<li class="toctree-l1"><a class="reference internal" href="cdist-type.html">12. cdist type</a></li>
<li class="toctree-l1"><a class="reference internal" href="cdist-types.html">13. cdist types</a></li>
<li class="toctree-l1"><a class="reference internal" href="cdist-explorer.html">14. Explorer</a></li>
<li class="toctree-l1"><a class="reference internal" href="cdist-messaging.html">15. Messaging</a></li>
<li class="toctree-l1"><a class="reference internal" href="cdist-parallelization.html">16. Parallelization</a></li>
<li class="toctree-l1"><a class="reference internal" href="cdist-reference.html">17. Reference</a></li>
<li class="toctree-l1"><a class="reference internal" href="cdist-best-practice.html">18. Best practice</a></li>
<li class="toctree-l1"><a class="reference internal" href="cdist-stages.html">19. Execution stages</a></li>
<li class="toctree-l1"><a class="reference internal" href="cdist-remote-exec-copy.html">20. Remote exec and copy commands</a></li>
<li class="toctree-l1"><a class="reference internal" href="cdist-hacker.html">21. Hacking</a></li>
<li class="toctree-l1"><a class="reference internal" href="cdist-troubleshooting.html">22. Troubleshooting</a></li>
</ul>
</div>
</div>
</nav>
<section data-toggle="wy-nav-shift" class="wy-nav-content-wrap">
<nav class="wy-nav-top" role="navigation" aria-label="top navigation">
<i data-toggle="wy-nav-top" class="fa fa-bars"></i>
<a href="index.html">cdist</a>
</nav>
<div class="wy-nav-content">
<div class="rst-content">
<div role="navigation" aria-label="breadcrumbs navigation">
<ul class="wy-breadcrumbs">
<li><a href="index.html">Docs</a> &raquo;</li>
<li>2. Why should I use cdist?</li>
<li class="wy-breadcrumbs-aside">
<a href="_sources/cdist-why.txt" rel="nofollow"> View page source</a>
</li>
</ul>
<hr/>
</div>
<div role="main" class="document" itemscope="itemscope" itemtype="http://schema.org/Article">
<div itemprop="articleBody">
<div class="section" id="why-should-i-use-cdist">
<h1>2. Why should I use cdist?<a class="headerlink" href="#why-should-i-use-cdist" title="Permalink to this headline"></a></h1>
<p>There are several motivations to use cdist, these
are probably the most popular ones.</p>
<div class="section" id="known-language">
<h2>2.1. Known language<a class="headerlink" href="#known-language" title="Permalink to this headline"></a></h2>
<p>Cdist is being configured in
<a class="reference external" href="https://en.wikipedia.org/wiki/Shell_script">shell script</a>.
Shell script is used by UNIX system engineers for decades.
So when cdist is introduced, your staff does not need to learn a new
<a class="reference external" href="https://en.wikipedia.org/wiki/Domain-specific_language">DSL</a>
or programming language.</p>
</div>
<div class="section" id="powerful-language">
<h2>2.2. Powerful language<a class="headerlink" href="#powerful-language" title="Permalink to this headline"></a></h2>
<p>Not only is shell scripting widely known by system engineers,
but it is also a very powerful language. Here are some features
which make daily work easy:</p>
<blockquote>
<div><ul class="simple">
<li>Configuration can react dynamicly on explored values</li>
<li>High level string manipulation (using sed, awk, grep)</li>
<li>Conditional support (<strong>if, case</strong>)</li>
<li>Loop support (<strong>for, while</strong>)</li>
<li>Support for dependencies between cdist types</li>
</ul>
</div></blockquote>
</div>
<div class="section" id="more-than-shell-scripting">
<h2>2.3. More than shell scripting<a class="headerlink" href="#more-than-shell-scripting" title="Permalink to this headline"></a></h2>
<p>If you compare regular shell scripting with cdist, there is one major
difference: When using cdist types,
the results are
<a class="reference external" href="https://en.wikipedia.org/wiki/Idempotence">idempotent</a>.
In practise that means it does not matter in which order you
call cdist types, the result is always the same.</p>
</div>
<div class="section" id="zero-dependency-configuration-management">
<h2>2.4. Zero dependency configuration management<a class="headerlink" href="#zero-dependency-configuration-management" title="Permalink to this headline"></a></h2>
<p>Cdist requires very litte on a target system. Even better,
in almost all cases all dependencies are usually fulfilled.
Cdist does not require an agent or a high level programming
languages on the target host: it will run on any host that
has a <strong>ssh server running</strong> and a posix compatible shell
(<strong>/bin/sh</strong>). Compared to other configuration management systems,
it does not require to open up an additional port.</p>
</div>
<div class="section" id="push-based-distribution">
<h2>2.5. Push based distribution<a class="headerlink" href="#push-based-distribution" title="Permalink to this headline"></a></h2>
<p>Cdist uses the push based model for configuration. In this
scenario, one (or more) computers connect the target hosts
and apply the configuration. That way the source host has
very little requirements: Cdist can even run on a sysadmin
notebook that is loosely connected to the network and has
limited amount of resources.</p>
<p>Furthermore, from a security point of view, only one machine
needs access to the target hosts. No target hosts will ever
need to connect back to the source host, which contains the
full configuration.</p>
</div>
<div class="section" id="highly-scalable">
<h2>2.6. Highly scalable<a class="headerlink" href="#highly-scalable" title="Permalink to this headline"></a></h2>
<p>If at some point you manage more hosts than can be handled from
a single source host, you can simply add more resources: Either
add more cores to one host or add hosts.
Cdist will utilise the given resources in parallel.</p>
</div>
</div>
</div>
</div>
<footer>
<div class="rst-footer-buttons" role="navigation" aria-label="footer navigation">
<a href="cdist-os.html" class="btn btn-neutral float-right" title="3. Supported Operating Systems" accesskey="n">Next <span class="fa fa-arrow-circle-right"></span></a>
<a href="cdist-intro.html" class="btn btn-neutral" title="1. cdist - usable configuration management" accesskey="p"><span class="fa fa-arrow-circle-left"></span> Previous</a>
</div>
<hr/>
<div role="contentinfo">
<p>
&copy; Copyright .
</p>
</div>
Built with <a href="http://sphinx-doc.org/">Sphinx</a> using a <a href="https://github.com/snide/sphinx_rtd_theme">theme</a> provided by <a href="https://readthedocs.org">Read the Docs</a>.
</footer>
</div>
</div>
</section>
</div>
<script type="text/javascript">
var DOCUMENTATION_OPTIONS = {
URL_ROOT:'./',
VERSION:'4.3.2',
COLLAPSE_INDEX:false,
FILE_SUFFIX:'.html',
HAS_SOURCE: true
};
</script>
<script type="text/javascript" src="_static/jquery.js"></script>
<script type="text/javascript" src="_static/underscore.js"></script>
<script type="text/javascript" src="_static/doctools.js"></script>
<script type="text/javascript" src="_static/js/theme.js"></script>
<script type="text/javascript">
jQuery(function () {
SphinxRtdTheme.StickyNav.enable();
});
</script>
</body>
</html>