diff options
Diffstat (limited to 'doc/client/index.txt')
| -rw-r--r-- | doc/client/index.txt | 19 |
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 |