summaryrefslogtreecommitdiffstats
path: root/doc/architecture.xml
diff options
context:
space:
mode:
authorNarayan Desai <desai@mcs.anl.gov>2006-01-23 22:35:40 +0000
committerNarayan Desai <desai@mcs.anl.gov>2006-01-23 22:35:40 +0000
commitedca0b698637c3fd0a70af7e4752a46afca938d3 (patch)
tree658fad717833200ccb4e3725c811ccce7c10fc8d /doc/architecture.xml
parent8ca8a153dfc6bd81ede9f5cff1ee3f111ae053ee (diff)
downloadbcfg2-edca0b698637c3fd0a70af7e4752a46afca938d3.tar.gz
bcfg2-edca0b698637c3fd0a70af7e4752a46afca938d3.tar.bz2
bcfg2-edca0b698637c3fd0a70af7e4752a46afca938d3.zip
last step of repo switches
git-svn-id: https://svn.mcs.anl.gov/repos/bcfg/trunk/bcfg2@1716 ce84e21b-d406-0410-9b95-82705330c041
Diffstat (limited to 'doc/architecture.xml')
-rw-r--r--doc/architecture.xml20
1 files changed, 13 insertions, 7 deletions
diff --git a/doc/architecture.xml b/doc/architecture.xml
index abb90c640..7c54fca45 100644
--- a/doc/architecture.xml
+++ b/doc/architecture.xml
@@ -72,7 +72,7 @@
</listitem>
<listitem>
<para>
- Generators and administrative applications.
+ Plugins and administrative applications.
</para>
</listitem>
<listitem>
@@ -104,6 +104,12 @@
simple as possible. The normal configuration process consists of
four main steps:</para>
+<!-- <procedure> -->
+<!-- <title>Bcfg2 Client Execution Process</title> -->
+
+<!-- <step>foo</step> -->
+<!-- </procedure> -->
+
<variablelist>
<varlistentry>
<term>Probe Execution</term>
@@ -316,18 +322,18 @@
literal configuration information. After the abstract
configuration is created, each configuration entry must
be bound to a client-specific value. The Bcfg2 server
- uses generators to provide these client-specific bindings.
+ uses plugins to provide these client-specific bindings.
</para>
<para>
The Bcfg2 server core contains a dispatch table that
- describes which generator can handle requests of a
- particular type. The responsible generator is located
+ describes which plugins can handle requests of a
+ particular type. The responsible plugin is located
for each entry. It is called, passing in the
configuration entry and the client's metadata. The
- behavior of generators is explicitly undefined, so as to
- allow maximum flexibility. The behavior of the stock
- generators is documented elsewhere in this manual.
+ behavior of plugins is explicitly undefined, so as to
+ allow maximum flexibility. The behaviors of the stock
+ plugins are documented elsewhere in this manual.
</para>
<para>