summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorNarayan Desai <desai@mcs.anl.gov>2005-09-02 15:24:33 +0000
committerNarayan Desai <desai@mcs.anl.gov>2005-09-02 15:24:33 +0000
commit52d121a7926ec9d856d9224e18fa55ba6cf10ad0 (patch)
tree892f4d81a48c3f130821757efe98fccce0b4e7d9
parentfd8b3e916044f31d81d7297a914d7c6a33e2e464 (diff)
downloadbcfg2-52d121a7926ec9d856d9224e18fa55ba6cf10ad0.tar.gz
bcfg2-52d121a7926ec9d856d9224e18fa55ba6cf10ad0.tar.bz2
bcfg2-52d121a7926ec9d856d9224e18fa55ba6cf10ad0.zip
Delete: doc/SETUP
}(Logical change 1.294) git-svn-id: https://svn.mcs.anl.gov/repos/bcfg/trunk/bcfg2@1173 ce84e21b-d406-0410-9b95-82705330c041
-rw-r--r--doc/SETUP37
1 files changed, 0 insertions, 37 deletions
diff --git a/doc/SETUP b/doc/SETUP
deleted file mode 100644
index d99ddaa27..000000000
--- a/doc/SETUP
+++ /dev/null
@@ -1,37 +0,0 @@
-$Id: $
-
-This document describes how to setup a Bcfg2 repository from scratch.
-
-1. /etc/bcfg2.conf
-
-This file tells Bcfg2Server important bootstrapping information about
-where its repository is, and which configuration structuring agents
-and generators should be used to build client
-configurations. The list of structures and generators are comma
-delimited and must be importable by python from the
-Bcfg2.Server.(Generators|Structures) hierarchy (respectively). All
-options currently are in the [server] section.
-
-repository: top level of configuration file repository
-structures: comma delimited list of structuring agents to use.
-generators: comma delimited list of generators to use.
-metadata: path to the directory where metadata.xml (the client
- metadata setup) resides.
-
-2. metadata/metadata.xml
-
-This file defines metadata constructs for all known systems. This file
-contains two types of declarations: one for clients, including an
-attribute for client image, and client nodes for class membership and
-attributes. See the example file for more info. This file doesn't
-need to be exhaustively written: bcfg2 will soon support defaults (to
-support environments where machines are frequently added) and default
-profiles.
-
-3. The repository
-
-Structuring agents and generators are responsible for contructing
-client configurations. All of these currently use FAM to coherently
-cache files on disk, with notifications upon file changes. The
-repository contains a directory for each of these; which is structured
-according to the needs of that generator/structure. \ No newline at end of file