[Fai-commit] r4495 - trunk/doc

[lange at alioth.debian.org]

Author: lange
Date: 2007-08-12 13:40:36 +0000 (Sun, 12 Aug 2007)
New Revision: 4495

Modified:
   trunk/doc/fai-guide.sgml
Log:
remove section about revision control for FAI configuration


Modified: trunk/doc/fai-guide.sgml
===================================================================
--- trunk/doc/fai-guide.sgml	2007-08-12 13:38:44 UTC (rev 4494)
+++ trunk/doc/fai-guide.sgml	2007-08-12 13:40:36 UTC (rev 4495)
@@ -2678,75 +2678,6 @@
 Then, you will want to set the variable <example>install=0</example> in the xen-tools config for
 that host(in previous versions of xen-tools, this was <tt>no-install=1</tt>).
 
-<sect id=generalscm>Using revision control for FAI configuration<p>
-If there is a team of administrators involved, a revision control/sourcecode
-management system like CVS can make coordination easier: many people can 
-work on the configuration files simultaneously, while the system helps
-avoiding conflicts (and if they occur it helps resolving them). Another
-advantage lies in <em>branching</em>: while the administrator works out a 
-new configuration and tries it out using a test system, other clients aren't
-disturbed in any way, because they use another <em>branch</em> of the
-configuration. </p>
-<sect1 id=cvs>Setting up FAI for CVS based configuration<p>
-First you should setup a CVS repository and within it a module to store the
-FAI configuration files. In this example a CVS pserver will be used for
-<em>read-only</em> access to the configuration files by the clients, while
-ssh is used for the developers access (rw)<footnote>CVS is quite flexible 
-when it comes to different methods of access, so I recommend you to read 
-further documentation to find the optimal solution in your
-environment</footnote>. </p>
-
-<p>The relevant variables in &fc; and &mfnc; for CVS are:
-<taglist>
-  <tag><var>FAI_LOCATION</var></tag>
-    <item>
-    This variable <strong>must not</strong> be set if you want to use CVS.
-    </item>
-  <tag><var>FAI_CVSROOT</var></tag>
-    <item>
-    contains the cvsroot where the configuration is stored.
-	<example>
-	FAI_CVSROOT=":pserver:client at cvs.local.net:/var/lib/cvs"
-	</example>
-    </item>
-  <tag><var>FAI_CVSMODULE</var></tag>
-    <item>
-      contains the module in the cvsroot where the configuration is stored.
-	<example>
-	FAI_CVSMODULE="config"
-	</example>
-    </item>
-  <tag><var>FAI_CVSTAG</var></tag>
-    <item>
-      contains the <em>tag</em> of the CVS branch to
-      be checked out by the client<footnote>This is optional: if not set,
-      <em>HEAD</em> will be used, which corresponds to the most recent
-      revision.</footnote>.
-	<example>
-	FAI_CVSTAG="STABLE"
-	</example>
-    </item>
-<!--  <tag><var>FAI</var></tag>
-    <item><p>
-      Before checking out the configuration, the code copies the contents of
-      this directory after a sanity check (i
-      to <file>/tmp/$FAI_CVSMODULE</file>, then enters the
-      directory and does a <example>cvs update</example> instead of a
-      <example>cvs checkout</example>. This behaviour is used in connection
-      with system updates to record the changes within configuration files.
-    </p></item>
-    -->
-</taglist></p>
-
-<p> If you use a CVS pserver for storing configuration files, the file
-<file>/root/.cvspass</file> has to exist and be valid in the nfsroot. CVS
-uses this file to get the password for the pserver. The easiest way to
-create it is <example>cvs -d$FAI_CVSROOT login</example> and then copy
-the generated line from your <file>~/.cvspass</file> into
-<file>/root/.cvspass</file> in the nfsroot.</p>
-</sect1>
-</sect>
-
 <sect id=softupdate>Using FAI for online updates
 <p>FAI is even usable for system updates, using the same configuration
 as if initially installing. System update means updating the running