summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorBrenton Leanhardt <brenton.leanhardt@gmail.com>2008-06-26 08:55:03 -0400
committerBrenton Leanhardt <brenton.leanhardt@gmail.com>2008-06-26 13:04:06 -0400
commitc4dea95c8b5cc2d00dbf626fb4a10fe6533c4df3 (patch)
tree30a8e2f29c9492a0be60e7981fc3e7b1a9084738
parent711f8aeb9f5a872118c3c2e4b54a09a61d47cee8 (diff)
downloadtools-c4dea95c8b5cc2d00dbf626fb4a10fe6533c4df3.tar.gz
tools-c4dea95c8b5cc2d00dbf626fb4a10fe6533c4df3.tar.xz
tools-c4dea95c8b5cc2d00dbf626fb4a10fe6533c4df3.zip
Adding more documentation for Repo machine creation
-rw-r--r--everest-repo/everest-repo-1.0.0/docs/en-US/Cookbook.xml40
1 files changed, 40 insertions, 0 deletions
diff --git a/everest-repo/everest-repo-1.0.0/docs/en-US/Cookbook.xml b/everest-repo/everest-repo-1.0.0/docs/en-US/Cookbook.xml
index d37ebbe..d41309b 100644
--- a/everest-repo/everest-repo-1.0.0/docs/en-US/Cookbook.xml
+++ b/everest-repo/everest-repo-1.0.0/docs/en-US/Cookbook.xml
@@ -79,6 +79,9 @@
<para>install the &REPORPM;</para>
</listitem>
<listitem>
+ <para>Kick off the bootstrap process</para>
+ </listitem>
+ <listitem>
<para>Replicate
<application>cobbler</application>
to pull down the bits and
@@ -111,6 +114,43 @@
</section>
<section>
+ <title>Starting the bootstrap process</title>
+ <para>
+ As with installing the &REPORPM; this step is
+ also typically handled via
+ <application>kickstart</application> (ie,
+ turned on via
+ <application>chkconfig</application>). That
+ being said, if you turning a machine that
+ already has an operating system into a Repo
+ machine this step will need to be run manually.
+
+ <screen>
+/sbin/service everest-repo-bootstrap start
+ </screen>
+ </para>
+ <note>
+ <title>Note</title>
+ <para>
+ This step is designed to work
+ "offline" since all the
+ external dependencies are
+ pulled down via the &REPORPM;.
+ That being said there are
+ external factors than can cause
+ it to fail. If you suspect a
+ Repo machine is not configured
+ correctly it is always safe to
+ run this command multiple times
+ as
+ <application>puppet</application>
+ will only perform outstanding
+ tasks.
+ </para>
+ </note>
+ </section>
+
+ <section>
<title>Replicate cobbler data</title>
<para>
The simplest way to do this is to use