Sophie

Sophie

distrib > Fedora > 17 > i386 > media > updates > by-pkgid > b50d8ee6d7871fcc13c0677a9364ed59 > files > 336

bcfg2-doc-1.3.0-1.fc17.noarch.rpm



<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
  "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">


<html xmlns="http://www.w3.org/1999/xhtml">
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
    
    <title>Goals &mdash; Bcfg2 1.3.0 documentation</title>
    
    <link rel="stylesheet" href="../_static/default.css" type="text/css" />
    <link rel="stylesheet" href="../_static/pygments.css" type="text/css" />
    
    <script type="text/javascript">
      var DOCUMENTATION_OPTIONS = {
        URL_ROOT:    '../',
        VERSION:     '1.3.0',
        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/sidebar.js"></script>
    <link rel="shortcut icon" href="../_static/favicon.ico"/>
    <link rel="top" title="Bcfg2 1.3.0 documentation" href="../index.html" />
    <link rel="up" title="Detailed Bcfg2 Architecture" href="index.html" />
    <link rel="next" title="The Bcfg2 Client" href="client.html" />
    <link rel="prev" title="Detailed Bcfg2 Architecture" href="index.html" />
 
<link rel="stylesheet" href="../_static/bcfg2.css" type=""/>

  </head>
  <body>

<div style="text-align: left; padding: 10px 10px 15px 15px">
<a href="../index.html"><img src="../_static/bcfg2_logo.png" border="0" alt="sampledoc"/></a>
</div>

    <div class="related">
      <h3>Navigation</h3>
      <ul>
        <li class="right" style="margin-right: 10px">
          <a href="../genindex.html" title="General Index"
             accesskey="I">index</a></li>
        <li class="right" >
          <a href="../py-modindex.html" title="Python Module Index"
             >modules</a> |</li>
        <li class="right" >
          <a href="client.html" title="The Bcfg2 Client"
             accesskey="N">next</a> |</li>
        <li class="right" >
          <a href="index.html" title="Detailed Bcfg2 Architecture"
             accesskey="P">previous</a> |</li>
	<li><a href="../index.html">home</a> |&nbsp;</li>
	<!--<li><a href="../search.html">search</a> |&nbsp;</li>-->
	<li><a href="../help/index.html">help</a> |&nbsp;</li>
	<li><a href="../contents.html">documentation </a> &raquo;</li>

          <li><a href="../contents.html" >Bcfg2 documentation 1.3.0</a> &raquo;</li>
          <li><a href="index.html" accesskey="U">Detailed Bcfg2 Architecture</a> &raquo;</li> 
      </ul>
    </div>
  

    <div class="document">
      <div class="documentwrapper">
        <div class="bodywrapper">
          <div class="body">
            
  <div class="section" id="goals">
<span id="architecture-goals"></span><h1>Goals<a class="headerlink" href="#goals" title="Permalink to this headline">ΒΆ</a></h1>
<ul>
<li><p class="first"><strong>Model configurations using declarative semantics.</strong></p>
<p>Declarative semantics maximize the utility of configuration management
tools; they provide the most flexibility for the tool to determine
the right course of action in any given situation. This means that
users can focus on the task of describing the desired configuration,
while leaving the task of transitioning clients states to the tool.</p>
</li>
<li><p class="first"><strong>Configuration descriptions should be comprehensive.</strong></p>
<p>This means that configurations served to the client should be sufficient
to reproduce all desired functionality. This assumption allows the
use of heuristics to detect extra configuration, aiding in reliable,
comprehensive configuration definitions.</p>
</li>
<li><p class="first"><strong>Provide a flexible approach to user interactions.</strong></p>
<p>Most configuration management systems take a rigid approach to user
interactions; that is, either the client system is always correct,
or the central system is. This means that users are forced into an
overly proscribed model where the system asserts where correct data
is. Configuration data modification is frequently undertaken on both
the configuration server and clients. Hence, the existence of a single
canonical data location can easily pose a problem during normal tool
use. Bcfg2 takes a different approach.</p>
</li>
</ul>
<p>The default assumption is that data on the server is correct, however,
the client has the option to run in another mode where local changes are
catalogued for server-side integration. If the Bcfg2 client is run in dry
run mode, it can help to reconcile differences between current client
state and the configuration described on the server. The Bcfg2 client
also searches for extra configuration; that is, configuration that is
not specified by the configuration description. When extra configuration
is found, either configuration has been removed from the configuration
description on the server, or manual configuration has occurred on the
client. Options related to two-way verification and removal are useful
for configuration reconciliation when interactive access is used.</p>
<ul class="simple">
<li>Plugins and administrative applications.</li>
<li>Incremental operations.</li>
</ul>
</div>


          </div>
        </div>
      </div>
      <div class="sphinxsidebar">
        <div class="sphinxsidebarwrapper">
  <h4>Previous topic</h4>
  <p class="topless"><a href="index.html"
                        title="previous chapter">Detailed Bcfg2 Architecture</a></p>
  <h4>Next topic</h4>
  <p class="topless"><a href="client.html"
                        title="next chapter">The Bcfg2 Client</a></p>
  <h3>This Page</h3>
  <ul class="this-page-menu">
    <li><a href="../_sources/architecture/goals.txt"
           rel="nofollow">Show Source</a></li>
  </ul>
<div id="searchbox" style="display: none">
  <h3>Quick search</h3>
    <form class="search" action="../search.html" method="get">
      <input type="text" name="q" />
      <input type="submit" value="Go" />
      <input type="hidden" name="check_keywords" value="yes" />
      <input type="hidden" name="area" value="default" />
    </form>
    <p class="searchtip" style="font-size: 90%">
    Enter search terms or a module, class or function name.
    </p>
</div>
<script type="text/javascript">$('#searchbox').show(0);</script>
        </div>
      </div>
      <div class="clearer"></div>
    </div>
    <div class="related">
      <h3>Navigation</h3>
      <ul>
        <li class="right" style="margin-right: 10px">
          <a href="../genindex.html" title="General Index"
             >index</a></li>
        <li class="right" >
          <a href="../py-modindex.html" title="Python Module Index"
             >modules</a> |</li>
        <li class="right" >
          <a href="client.html" title="The Bcfg2 Client"
             >next</a> |</li>
        <li class="right" >
          <a href="index.html" title="Detailed Bcfg2 Architecture"
             >previous</a> |</li>
	<li><a href="../index.html">home</a> |&nbsp;</li>
	<!--<li><a href="../search.html">search</a> |&nbsp;</li>-->
	<li><a href="../help/index.html">help</a> |&nbsp;</li>
	<li><a href="../contents.html">documentation </a> &raquo;</li>

          <li><a href="../contents.html" >Bcfg2 documentation 1.3.0</a> &raquo;</li>
          <li><a href="index.html" >Detailed Bcfg2 Architecture</a> &raquo;</li> 
      </ul>
    </div>
    <div class="footer">
        &copy; Copyright 2009-2013, Narayan Desai.
      Last updated on Mar 20, 2013.
      Created using <a href="http://sphinx.pocoo.org/">Sphinx</a> 1.1.3.
    </div>
  </body>
</html>