summaryrefslogtreecommitdiffstats
path: root/doc/client/index.txt
diff options
context:
space:
mode:
authorSol Jerome <solj@ices.utexas.edu>2010-02-22 14:40:45 +0000
committerSol Jerome <solj@ices.utexas.edu>2010-02-22 14:40:45 +0000
commit999544fdb0760bbb048cadd4003227c268f272af (patch)
tree7b90843bd1e40d08064013874b80297146b966c8 /doc/client/index.txt
parent1095c93de739b3c91cc344e6cdd6cb7139bcd53c (diff)
downloadbcfg2-999544fdb0760bbb048cadd4003227c268f272af.tar.gz
bcfg2-999544fdb0760bbb048cadd4003227c268f272af.tar.bz2
bcfg2-999544fdb0760bbb048cadd4003227c268f272af.zip
doc: formatting fixes
Signed-off-by: Sol Jerome <solj@ices.utexas.edu> git-svn-id: https://svn.mcs.anl.gov/repos/bcfg/trunk/bcfg2@5738 ce84e21b-d406-0410-9b95-82705330c041
Diffstat (limited to 'doc/client/index.txt')
-rw-r--r--doc/client/index.txt19
1 files changed, 13 insertions, 6 deletions
diff --git a/doc/client/index.txt b/doc/client/index.txt
index 438e43dcd..d0e7bd9a6 100644
--- a/doc/client/index.txt
+++ b/doc/client/index.txt
@@ -6,14 +6,21 @@ The Bcfg2 Client
================
The Bcfg2 client is responsible for determining what reconfiguration
-operations must be undertaken on the client, but does not perform any
-processing of the target configuration description. We chose this
+operations must be undertaken on the client, but does not perform
+any processing of the target configuration description. We chose this
architecture, as opposed to one with a smarter client, for a few reasons:
-* Client failure forces administrators to perform an O(n) reconfiguration operation. Simpler code is easier to debug and maintain.
-* Minimize the bootstrap size; a complicated client can require more aspects of the system to function in order for reconfiguration to work.
-* Isolate configuration generation functionality on the server, where it can be readily observed. This is the most complicated task that Bcfg2 performs.
-* The results of the configuration process fit a fairly simple model. We wanted to validate it. The result is that Bcfg2 has a programmable deployment engine that can be driven by anything that writes a compatible configuration description.
+* Client failure forces administrators to perform an O(n) reconfiguration
+ operation. Simpler code is easier to debug and maintain.
+* Minimize the bootstrap size; a complicated client can require more
+ aspects of the system to function in order for reconfiguration to work.
+* Isolate configuration generation functionality on the server, where
+ it can be readily observed. This is the most complicated task that
+ Bcfg2 performs.
+* The results of the configuration process fit a fairly simple model. We
+ wanted to validate it. The result is that Bcfg2 has a programmable
+ deployment engine that can be driven by anything that writes a
+ compatible configuration description.
.. toctree::
:maxdepth: 2