install-guide/devel/en_US beginninginstallation.xml, 1.11, 1.12 expert-quickstart.xml, 1.6, 1.7 pxe-server.xml, 1.3, 1.4 rpm-info.xml, 1.14, 1.15

Paul W. Frields (pfrields) fedora-docs-commits at redhat.com
Sat Oct 6 14:21:54 UTC 2007


Author: pfrields

Update of /cvs/docs/install-guide/devel/en_US
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv19650/en_US

Modified Files:
	beginninginstallation.xml expert-quickstart.xml pxe-server.xml 
	rpm-info.xml 
Log Message:
Add information on making an installation server using cobbler, for HTTP, NFS, or FTP services


Index: beginninginstallation.xml
===================================================================
RCS file: /cvs/docs/install-guide/devel/en_US/beginninginstallation.xml,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- beginninginstallation.xml	28 May 2007 00:45:06 -0000	1.11
+++ beginninginstallation.xml	6 Oct 2007 14:21:51 -0000	1.12
@@ -191,7 +191,7 @@
       </indexterm> PXE, you need a properly configured server, and a
       network interface in your computer that supports PXE.  For
       information on how to configure a PXE server, refer to <xref
-	linkend="ap-pxe-server"/>.
+	linkend="ap-install-server"/>.
     </para>
 
     <para>


Index: expert-quickstart.xml
===================================================================
RCS file: /cvs/docs/install-guide/devel/en_US/expert-quickstart.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- expert-quickstart.xml	22 Sep 2007 20:30:21 -0000	1.6
+++ expert-quickstart.xml	6 Oct 2007 14:21:51 -0000	1.7
@@ -86,7 +86,7 @@
 	  refer to <xref linkend="ap-medialess-install"/>.</para>
 	<para>For information on setting up a network boot server from
 	  which you can install &DISTRO;, refer to <xref
-	    linkend="ap-pxe-server"/>.</para>
+	    linkend="ap-install-server"/>.</para>
       </listitem>
     </orderedlist>
   </section>


Index: pxe-server.xml
===================================================================
RCS file: /cvs/docs/install-guide/devel/en_US/pxe-server.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- pxe-server.xml	15 Sep 2007 04:15:02 -0000	1.3
+++ pxe-server.xml	6 Oct 2007 14:21:51 -0000	1.4
@@ -10,7 +10,7 @@
 
 ]>
 
-<appendix id="ap-pxe-server">
+<appendix id="ap-install-server">
   <title>Setting Up a PXE Server</title>
   <note>
     <title>Experience Required</title>
@@ -18,99 +18,194 @@
       experience.  If you are a new user, you may want to install using
       minimal boot media or the distribution DVD instead.</para>
   </note>
-  <para>This section discusses how to set up a <firstterm>Pre-boot
-      eXecution Environment</firstterm> (<acronym>PXE</acronym>) boot
-    server for machines that cannot boot from CD, DVD, or USB media. PXE
-    is a special extension of services provided by the
-    <firstterm>Dynamic Host Configuration Protocol</firstterm>
-    (<acronym>DHCP</acronym>).  It uses a <firstterm>Trivial File
-      Transfer Protocol</firstterm> (<acronym>TFTP</acronym>) server to
-    provide minimal boot files to a network client.  To set up a PXE
-    boot service on a separate &DISTRO; server on the local network,
-    follow this procedure:</para>
-  <procedure>
-    <step>
-      <para>Install the <package>tftp-server</package>,
-	<package>dhcp</package>, and <package>syslinux</package>
-	packages:</para>
-      <screen><command>su -c 'yum install tftp-server
-	  dhcp syslinux'</command></screen>
-    </step>
-    <step>
-      <para>Edit the <filename>/etc/dhcpd.conf</filename> file to
-	configure the DHCP server.  The following example is a minimal
-	configuration for a network that uses the following
-	configuration:</para>
-      <itemizedlist>
-	<listitem>
-	  <para><systemitem
-	      class="ipaddress">192.168.1.0/24</systemitem>
-	    addressing</para>
-	</listitem>
-	<listitem>
-	  <para>Dynamic addresses provided between <systemitem
-	      class="ipaddress">192.168.1.200</systemitem> and
-	    <systemitem
-	      class="ipaddress">192.168.1.240</systemitem></para>
-	</listitem>
-	<listitem>
-	  <para>DHCP/PXE server at IP address <systemitem
-	      class="ipaddress">192.168.1.10</systemitem></para>
-	</listitem>
-	<listitem>
-	  <para>No other dynamic configuration provided</para>
-	</listitem>
-      </itemizedlist>
-      <screen><computeroutput><![CDATA[allow booting;
-allow bootp;
-ddns-update-style interim;
-ignore client-updates;
-
-subnet 192.168.1.0 netmask 255.255.255.0 {
-	  option subnet-mask 255.255.255.0;
-	  option broadcast-address 192.168.1.255;
-	  range dynamic-bootp 192.168.1.200 192.168.1.240;
-	  next-server 192.168.1.10;
-	  filename "pxelinux.0";
-}]]></computeroutput></screen>
-    </step>
-    <step>
-      <para>As the <systemitem class="username">root</systemitem> user,
-	copy the PXE boot image and &DISTRO; boot files to the TFTP
-	server directory.</para>
-      <screen><![CDATA[su -
-cd /tftpboot
-cp /usr/lib/syslinux/pxelinux.0 .]]></screen>
-    </step>
-    <step>
-      <para>Copy the <filename>vmlinuz</filename> and
-	<filename>initrd.img</filename> files from the <filename
-	  class="directory">pxeboot</filename> directory on distribution
-	media or a Web mirror to the <filename
-	  class="directory">/tftpboot</filename> directory.</para>
-    </step>
-    <step>
-      <para>Create a minimal <filename>/tftpboot/pxelinux.cfg/default</filename>
-	file:</para>
-      <screen><![CDATA[DEFAULT pxeboot
-TIMEOUT 50
-LABEL pxeboot
-      KERNEL vmlinuz
-      APPEND initrd=initrd.img
-ONERROR LOCALBOOT 0]]></screen>
-    </step>
-    <step>
-      <para>Turn on the <systemitem class="service">dhcpd</systemitem>,
-	<systemitem class="service">xinetd</systemitem> and <systemitem
-	  class="service">tftp</systemitem> services:</para>
-      <screen><![CDATA[su -c '/sbin/service dhcpd start'
-su -c '/sbin/service xinetd start'
-su -c '/sbin/chkconfig tftp on']]></screen>
-    </step>
-  </procedure>
-  <para>Boot the client system and either use the required keys or
-    configure its BIOS to boot from its network interface using PXE.  At
-    the boot prompt, hit <keycap>Enter</keycap> to boot the default
-    &DISTRO; installation image.  If an error occurs, the system boots
-    in its normal configuration, such as a local hard disk.</para>
+  <para>In the past, administrators needed to perform a great deal of
+    manual configuration to produce an installation server.  However, if
+    you have a &RHEL;, CentOS, or Fedora server on your local network,
+    you can use <package>cobbler</package> to perform these
+    tasks.</para>
+  <para>To perform the tasks in this section, switch to the <systemitem
+      class="username">root</systemitem> account with the command
+    <command>su -</command>.  As an alternative, you can run a command
+    with the <option>-c</option> option, using the form <command>su -c
+      '<replaceable>command</replaceable>'</command>.</para>
+  <section id="sn-install-cobbler">
+    <title>Setting Up <package>cobbler</package></title>
+    <para>To install <package>cobbler</package> use the following
+      command:</para>
+      <screen><command><![CDATA[yum -y install cobbler]]></command></screen>
+      <para>The <command>cobbler</command> command can check its own
+	settings for validity and report the results.  Run the following
+	command to check the settings:</para>
+      <screen><command><![CDATA[cobbler check]]></command></screen>
+      <para>Change the settings in the
+      <filename>/var/lib/cobbler/settings</filename> file to reflect the
+      IP address information for the server.  You must change at least
+      the <option>server</option> and <option>next_server</option>
+      options, although these options may point to the same IP
+      address.</para>
+    <para>If you are not already running a DHCP server, you should also
+      change the <option>manage_dhcp</option> option to
+      <userinput>1</userinput>.  If you are running a DHCP server,
+      configure it according to the instructions found in the
+      <package>syslinux</package> package documentation.  For more
+      information, refer to your local files
+      <filename>/usr/share/doc/syslinux-<replaceable>version</replaceable>/syslinux.doc</filename> 
+      and
+      <filename>/usr/share/doc/syslinux-<replaceable>version</replaceable>/pxelinux.doc</filename>.</para>
+  </section>
+  <section id="sn-cobbler-setup-distro">
+    <title>Setting Up the Distribution</title>
+    <para>To set up a distribution from a full &DISTRO; DVD or ISO
+      image, use this procedure.</para>
+    <note>
+      <title>Network Locations</title>
+      <para>To create a local mirror from an existing network source,
+	skip this section and refer instead to <xref
+	  linkend="sn-cobbler-mirror"/>.</para>
+    </note>
+    <procedure>
+      <step>
+	<para>If you are using a DVD disc or ISO image, Create a
+	  directory mount point:</para>
+	<screen><command><![CDATA[mkdir /mnt/dvd]]></command></screen>
+	<para>To mount a physical DVD disc, use the following
+	  command:</para>
+	<screen><command><![CDATA[mount -o context=system_u:object_r:httpd_sys_content_t:s0 /dev/dvd /mnt/dvd]]></command></screen>
+	<para>To mount a DVD ISO image, use the following
+	  command:</para>
+	<screen><command><![CDATA[mount -ro loop,context=system_u:object_r:httpd_sys_content_t:s0 /path/to/image.iso /mnt/dvd]]></command></screen>
+      </step>
+      <step>
+	<para>To support NFS installation, create a file
+	  <filename>/etc/exports</filename> and add the following line
+	  to it:</para>
+	<screen><![CDATA[/mnt/dvd *(ro,async)]]></screen>
+	<para>Start the NFS server using the following commands:</para>
+	<screen><command><![CDATA[/sbin/service rpcbind start
+/sbin/service nfs start]]></command></screen>
+      </step>
+      <step>
+	<para>To support HTTP installation, use <command>yum</command>
+	  to install the Apache web server if it is not already
+	  installed:</para>
+	<screen><command><![CDATA[yum -y install httpd]]></command></screen>
+	<para>Make a link to the mounted disc in the Apache public
+	  content area:</para>
+	<screen><command>ln -s /mnt/dvd /var/www/html/<replaceable>distro</replaceable></command></screen>
+      </step>
+    </procedure>
+  </section>
+  <section id="sn-cobbler-mirror">
+    <title>Mirroring a Network Location</title>
+    <para>If you do not have discs or ISO images for a distribution, you
+      can use <command>cobbler</command> to create an installation
+      server.  The <command>cobbler</command> command can fetch the
+      distribution over the network as part of the import
+      process.</para>
+    <para>Locate the distribution on the network.  The location may be
+      on the local network or reached at a remote site via FTP, HTTP, or
+      rsync protocols.  Note the URI, which will be in one of the
+      following forms:</para>
+    <itemizedlist>
+      <listitem>
+	<para><uri>http://mirror.example.com/pub/&FEDLC;/linux/releases/&DISTROVER;/&DISTRO;/<replaceable>arch</replaceable>/os</uri></para>
+      </listitem>
+      <listitem>
+	<para><uri>ftp://mirror.example.com/pub/&FEDLC;/linux/releases/&DISTROVER;/&DISTRO;/<replaceable>arch</replaceable>/os</uri></para>
+      </listitem>
+      <listitem>
+	<para><uri>rsync://mirror.example.com/&FEDLC;/linux/releases/&DISTROVER;/&DISTRO;/<replaceable>arch</replaceable>/os</uri></para>
+      </listitem>
+    </itemizedlist>
+  </section>
+  <section id="sn-cobbler-import">
+    <title>Importing the Distribution</title>
+    <para>To offer a distribution through more than one
+      installation method, perform additional <command>cobbler
+	import</command> tasks using a different name for each method.
+      For best results, use the installation method as part of the name,
+      so it appears in the client's boot menu.</para>
+    <procedure>
+      <step>
+	<para>To import the DVD disc or ISO distribution into
+	  <command>cobbler</command>, run this command:</para>
+	<screen><command>cobbler import --path=/mnt/dvd --name=<replaceable>distro_name</replaceable></command></screen>
+	<para>For <replaceable>distro_name</replaceable>, substitute a
+	  meaningful name for the distribution.</para>
+	<para>To import a local or remote network distribution into
+	  <command>cobbler</command>, run this command.  Replace
+	  <replaceable>network_URI</replaceable> with the URI you found
+	  in <xref linkend="sn-cobbler-mirror"/>, and
+	  <replaceable>distro_name</replaceable> as above:</para>
+	<screen><command>cobbler import --mirror=<replaceable>network_URI</replaceable> --name=<replaceable>distro_name</replaceable></command></screen>
+	<important>
+	  <title>Importing a Source</title>
+	  <para>When <command>cobbler</command> imports a distribution
+	    with the commands above, it copies all the files to the
+	    server's local storage, which may take some time.</para>
+	</important>
+	<para>If you do not want to make local copies of the
+	  distribution because clients can already reach its location,
+	  use the <option>--available-as</option> option.</para>
+	<screen><command>cobbler import --path=/mnt/dvd --name=<replaceable>distro_name</replaceable> --available-as=<replaceable>network_URI</replaceable></command>
+	  <command>cobbler import --mirror=<replaceable>network_URI</replaceable> --name=<replaceable>distro_name</replaceable> --available-as=<replaceable>network_URI</replaceable></command>
+</screen>
+	<para>For <replaceable>nework_URI</replaceable>, substitute the
+	  appropriate network location of the distribution. This URI
+	  indicates how the server makes the distribution available to
+	  its clients.  The examples above assume that your
+	  <command>cobbler</command> server reaches the mirror location
+	  at the same URI as the clients.  If not, substitute an
+	  appropriate URI for the <option>--mirror</option> option.  The
+	  following examples are URI locations that work if you have
+	  been following the procedures in this section, and your
+	  server's IP address is <systemitem
+	    class="ipaddress">192.168.1.1</systemitem>:</para>
+	<itemizedlist>
+	  <listitem>
+	    <para><uri>nfs://<replaceable>192.168.1.1</replaceable>:/mnt/dvd</uri></para>
+	  </listitem>
+	  <listitem>
+	    <para><uri>http://<replaceable>192.168.1.1</replaceable>:/distro</uri></para>
+	  </listitem>
+	</itemizedlist>
+	<para>If necessary, replace
+	  <replaceable>192.168.1.1</replaceable> with the IP address for
+	  your <command>cobbler</command> server.</para>
+      </step>
+      <step>
+	<para>Run the command <command>cobbler sync</command> to apply
+	  the changes.  To check that your <command>cobbler</command>
+	  server is listening on the correct ports, use the
+	  <command>netstat -lp</command> command.</para>
+	<important>
+	  <title>Firewall Considerations</title>
+	  <para>Depending on your server's configuration, you may need
+	    to use the <command>system-config-securitylevel</command>
+	    command to permit access to some or all of these network
+	    services:</para>
+	  <itemizedlist>
+	    <listitem>
+	      <para>67 or bootps, for the DHCP/BOOTP server</para>
+	    </listitem>
+	    <listitem>
+	      <para>69 or tftp, for providing the PXE loader</para>
+	    </listitem>
+	    <listitem>
+	      <para>80 or http, if the <command>cobbler</command> server
+		is to provide HTTP installation service</para>
+	    </listitem>
+	    <listitem>
+	      <para>20 and 21 or ftp, if the <command>cobbler</command>
+		server is to provide FTP installation service</para>
+	    </listitem>
+	    <listitem>
+	      <para>111 or sunrpc, if the <command>cobbler</command>
+		server is to provide NFS installation service</para>
+	    </listitem>
+	  </itemizedlist>
+	</important>
+      </step>
+    </procedure>
+  </section>
 </appendix>


Index: rpm-info.xml
===================================================================
RCS file: /cvs/docs/install-guide/devel/en_US/rpm-info.xml,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- rpm-info.xml	22 Sep 2007 17:54:17 -0000	1.14
+++ rpm-info.xml	6 Oct 2007 14:21:51 -0000	1.15
@@ -23,6 +23,10 @@
   <title>Fedora 8 Installation Guide</title>
   <desc>Provides documentation for the installation process.</desc>
   <changelog order="newest-first">
+    <revision date="2007-10-06" number="7.92.2">
+      <author worker="PaulWFrields"/>
+      <details>Add cobbler information for install servers</details>
+    </revision>
     <revision date="2007-09-22" number="7.92.1">
       <author worker="PaulWFrields"/>
       <details>Update some content for F8</details>




More information about the Fedora-docs-commits mailing list