Diff for /doc/build/suse10.1_install.frag between versions 1.1 and 1.2

version 1.1, 2006/10/09 21:12:16 version 1.2, 2006/10/10 20:32:58
Line 1 Line 1
 <h1>Installing LON-CAPA on a minimal SuSE Linux Enterprise Server (SLES) 10</h1>  <h1>Installing LON-CAPA on a minimal SuSE Linux 10.1 System</h1>
 <p>  <p>
 This document guides you through the process of setting up a new LON-CAPA  This document guides you through the process of setting up a new LON-CAPA
 server running SuSE Linux Enterprise Server 10 (SLES 10) with a minimum of packages installed.    server running SuSE Linux 10.1 with a minimum of packages installed.  
 The computer will be configured solely as a LON-CAPA server and will be   The computer will be configured solely as a LON-CAPA server and will be 
 expected to have no other services running.  Your server is expected to have  expected to have no other services running.  Your server is expected to have
 a reasonably fast connection to the internet.  a reasonably fast connection to the internet.
Line 12  More information is available at Line 12  More information is available at
   
 <h2>Before you begin</h2>  <h2>Before you begin</h2>
 <p>  <p>
 Installing Linux is getting easier and easier.    Installing Linux is getting easier and easier. You will be required to log in to the machine and execute some routine Unix commands.  Familiarity with the Apache web server, mod_perl, perl, and MySQL are not required to install and run LON-CAPA.
 You will be required to log in to the machine and execute  
 some routine Unix commands.  Familiarity with the Apache web server, mod_perl,   
 perl, and MySQL are not required to install and run LON-CAPA.  
 </p>  </p>
   
 <h2>Installation Overview</h2>  <h2>Installation Overview</h2>
Line 23  perl, and MySQL are not required to inst Line 20  perl, and MySQL are not required to inst
 The installation process takes the following steps:  The installation process takes the following steps:
 </p>  </p>
 <ol>  <ol>
   <li> Obtain SLES 10 installation media</li>    <li> Obtain SuSE 10.1 installation media (DVD, or CDs)</li>
   <li> Determine Network Settings</li>    <li> Determine Network Settings</li>
   <li> Install SLES 10</li>    <li> Install Suse 10.1</li>
   <li> Update your system </li>    <li> Update your system </li>
   <li> Install LON-CAPA </li>    <li> Install LON-CAPA </li>
   <li> Create a Domain Coordinator </li>    <li> Create a Domain Coordinator </li>
Line 33  The installation process takes the follo Line 30  The installation process takes the follo
   <li> Log in to LON-CAPA </li>    <li> Log in to LON-CAPA </li>
 </ol>  </ol>
   
 <h2>Obtain SuSE Linux Enterprise Server 10</h2>  <h2>Obtain SuSE Linux 10.1</h2>
 <p>  <p>
 SuSE ISO files can be obtained from the Novell site: <a href="http://www.novell.com/products/server/">http://www.novell.com/products/server/</a>.    A SuSE 10.1 iso for burning to DVD can be obtained from the Novell download site: <a href="http://download.novell.com/index.jsp">http://download.novell.com/index.jsp</a>, or from an opensuse mirror site - <a href="http://en.opensuse.org/Mirrors_Released_Version">http://en.opensuse.org/Mirrors_Released_Version</a>.  You will also find links to sites with iso files for burning to CD, if you burning CDs is more convenient for you. 
 </p>   </p> 
   
 <h2>Determine Network Settings</h2>  <h2>Determine Network Settings</h2>
 <p>  <p>
 You will need to know the following network settings for your installation.    You will need to know the following network settings for your installation.  
Line 52  DHCP is <em>not</em> supported. Line 48  DHCP is <em>not</em> supported.
   <li>domain name server(s) </li>    <li>domain name server(s) </li>
 </ul>  </ul>
   
 <h2>Minimal SLES 10 Install</h2>  <h2>Minimal SuSE 10.1  Install</h2>
 <p>  <p>
 Installing SuSE Linux Enterprise Server is quite easy if you've installed Linux products  Installing SuSE 10.1 is quite easy if you've installed Linux products
 before.  Some documentation is available from   before.  Some documentation is available from 
 <a href="http://www.novell.com/documentation/sles10/">  <a href="http://www.novell.com/documentation/suse101/">
 http://www.novell.com/documentation/sles10/</a>.<br /><br />  http://www.novell.com/documentation/suse101/</a>.<br /><br />
 Most of the subsequent installation screens are self explanatory.  Most of the subsequent installation screens are self explanatory.
 There are a few steps that require comment and are dealt with below.  There are a few steps that require comment and are dealt with below.
 </p>  </p>
 <dl style="list-style:square outside none">  <dl style="list-style:square outside none">
      <dt>Desktop Selection</dt>
      <dd>Click <i>Select</i> and choose <i>Text Mode</i> 
    <dt>Partitioning your Drive</dt>     <dt>Partitioning your Drive</dt>
    <dd>For a LON-CAPA library server (i.e., the main server used      <dd>For a LON-CAPA library server (i.e., the main server used 
        for permanent storage of course and user data),          for permanent storage of course and user data), 
Line 69  There are a few steps that require comme Line 67  There are a few steps that require comme
        simplifies future upgrades of the operating system.         simplifies future upgrades of the operating system.
        If you are adding an additional access server to an          If you are adding an additional access server to an 
        existing LON-CAPA domain, this does not apply as no          existing LON-CAPA domain, this does not apply as no 
        permanent data are stored on an access server.         permenent data are stored on an access server.
        As LON-CAPA resource files are stored in the /home directory,         As LON-CAPA resource files are stored in the /home directory,
        the majority of the disk space should be allocated here.             the majority of the disk space should be allocated here.    
        If you have 20 GB of space for SLES10, /home should         If you have 20 GB of space for SuSE 10.1, /home should
        receive at least 10 to 12 gigs. Since MySQL uses the /var          receive at least 10 to 12 gigs. Since MySQL uses the /var 
        filesystem to store its databases you should have as least          filesystem to store its databases you should have as least 
        4 gigs of space available on /var.  Be sure to          4 gigs of space available on /var.  Be sure to 
        include adequate swap space.  A minimum is 512 Megs, but you should         include adequate swap space.  A minimum is 512 Megs, but you should
        typically have 1 or 2x as much swap space as you do physical RAM.         typically have 1 or 2x as much swap space as you do physical RAM.
        </dd>         </dd>
    <dt>Software Selection</dt>  
    <dd>   
    Installation of the minimum set of packages is recommended.  This will involve unchecking all checkboxes except for the base SuSE installation.</dd>  
 </dl>  </dl>
 <p>Once you system has rebooted, you will use yast to complete the configuration. Change the following settings:  <p>Once you system has rebooted, you will use yast to complete the configuration. Change the following settings:
 <dl style="list-style:square outside none">  <dl style="list-style:square outside none">
      <dt>Firewall</dt>
      <dd>Enable the firewall, and allow the the following services: web services (http and https) and login services (secure shell). Use the "Expert" option to open the following ports for TCP services: 8080 5663.</dd>
    </p>
    <p>       
    <dt>Network Configuration</dt>     <dt>Network Configuration</dt>
    <dd>LON-CAPA will <b>not</b> work with a machine set up to use a dynamic     <dd>LON-CAPA will <b>not</b> work with a machine set up to use a dynamic
        IP address.  When configuring your network card, you should include you static IP address, netmask, host name information (e.g., host name = tmp1, domain = lite.msu.edu), as well as name servers and gateway.         IP address.  When configuring your network card, you should include host name information (e.g., host name = tmp1, domain = lite.msu.edu), as well as name server. Other settings (ip address, gateway, netmask will have been set when you included them in the boot configuration).
    </dd>     </dd>
    <dt>Online update</dt>     <dt>Registration</dt>
    <dd>Indicate "Yes" when prompted to "run online update now?"</dd>     <dd>It is recommended that you register your server with Novell, for future updates during the installation process, however it is recommended that you indicate "No" when prompted to "run online update now?" after completing the registration process.</dd>
    </dt>     </dt>
 </dl>  </dl>
 <p>  <p>
 Finish installing your server, read the "readme", reboot and log in as root.  Finish installing your server, read the "readme", reboot and log in as root. Follow the instructions found in the article: <a href="http://susewiki.org/index.php?title=Wrestling_Zen_to_Work">Wrestling Zen to Work</a> to fix package management and to run the online update, and lastly ensure that the zen management daemon is running by executing:  
 </p>  
 <h2>Configure Firewall Settings</h2>  
 <p>After reboot you should start yast, and select Security and Users -> Firewall. At step 2 include the following services: HTTP, HTTP with SSL, and Secure Shell.  Use the "Expert..." option to add additional TCP services on ports 5663 and 8080.      
 </p>  </p>
   <pre>
   /etc/init.d/novell-zmd start
   </pre>
 <h2>Change software sources for your system</h2>  <h2>Change software sources for your system</h2>
   <p>If you do not already have a SuSE 10.1 installation source at your location, you may want to consider creating one from the 5 iso files for CDs 1 - 5. Proceed as follows (e.g., for 32 bit):</p>
   <pre>
   mkdir -p suse101/CD1
   mount -o ro,loop SUSE-Linux-10.1-GM-i386-CD1.iso /mnt
   cp -rv /mnt/* suse101/CD1
   umount /mnt
   </pre>  
   <p>
   Repeat those steps with CD2, CD3, CD4 and CD5.</p>
 <p>  <p>
 You will use yast to import packages required for LON-CAPA.<br />  Next you will use yast to import packages required for LON-CAPA.<br />
 Execute:  Execute:
 </p>  </p>
 <pre>  <pre>
 yast  yast
 </pre>  </pre>
 <p>  <p>
 Select "Change Source of Installation". The media you used to install SLES10 will be listed as an installation source.  You may also wish to create a local repository by copying the contents of the RPM directories on the five CDs to a local directory to avoid the need to flip CDs during LON-CAPA installation.  Information about building a local repository is available at:<a href="http://portal.suse.com/sdb/en/2004/02/yast_instsrc.html">http://portal.suse.com/sdb/en/2004/02/yast_instsrc.html</a>.  Select "Installation Source" and change to either point at an internet installation repository close to your location (see <a href="http://en.opensuse.org/Mirrors_Released_Version">http://en.opensuse.org/Mirrors_Released_Version</a>), or a local institutional source you have built from the SuSE 10.1 CDs, or if using a DVD you may prefer to continue to point at the installation DVD.
 </p>  </p>
 <h3>Add an additional installation source</h3>  <h3>Add an additional installation source</h3>
 <p>Add the LON-CAPA SLES 10 repository as an additional installation source, so software installation in yast will have access to two repositories - a SuSE/Novell source (for packages included for the standard distribution) and the LON-CAPA repository (for extra packages needed to run LON-CAPA). For the LON-CAPA source you will use:  <p>Add the LON-CAPA SuSE 10.1 repository as an additional installation source. once this is done, software installation in yast should then have access to three repositories - a YUM source for SuSE updates (established when you run online update from yast), an installation source (for packages included in the standard distribution) and the LON-CAPA repository (for extra packages needed to run LON-CAPA). For the LON-CAPA source you will use:
 <dl style="list-style:square outside none">  <dl style="list-style:square outside none">
 <dd>Protocol</dd>  <dd>Protocol</dd>
 <dt>HTTP</dt>  <dt>HTTP</dt>
 <dd>Server Name</dd>  <dd>Server Name</dd>
 <dt>install.loncapa.org</dt>  <dt>install.loncapa.org</dt>
 <dd>Directory on server</dd>  <dd>Directory on server</dd>
 <dt>suse/sles10/</dt>  <dt>suse/10.1/</dt>
 <dd>Authentication</dd>  <dd>Authentication</dd>
 <dt>Anonymous</dt>  <dt>Anonymous</dt>
 </dl>  </dl>
 After saving this configuration information for the LON-CAPA repository, quit yast.    After saving this configuration information for the LON-CAPA repository, you will need to import a public LON-CAPA key, before the catalog is read, and the repository is available to you. Quit yast.    
 </p>  </p>
   <h2>Installing LON-CAPA</h2>
 <h3>Install prerequisites</h3>  <h3>Install prerequisites</h3>
 <p> Execute: </p>  <p> Execute: </p>
 <pre>  <pre>
 yast -i LONCAPA-prerequisites  yast -i LONCAPA-prerequisites
 </pre><p>  </pre><p>
 This may take a moment due to LON-CAPA's large number of dependencies.  This may take a moment due to LON-CAPA's large number of dependencies. When prompted to choose an apache package, select apache, NOT apache2, then click Solve.  
 </p>  </p>
 <h3>Retrieve and execute LON-CAPA setup program</h3>  <h3>Retrieve and execute LON-CAPA setup program</h3>
 <p>  <p>
 Retrieve the LON-CAPA setup with one of the following commands:  Retrieve the LON-CAPA setup with the following command:
 </p>  </p>
 <pre>  <pre>
 wget http://install.loncapa.org/versions/suse/sles10/sles10_install.tar  wget http://install.loncapa.org/versions/suse/10.1/suse10.1_install.tar
 </pre>  </pre>
 <p>  <p>
 Extract the archive with the following command:  Extract the archive with the following command:
 </p>  </p>
 <pre>  <pre>
 tar xf sles10_install.tar  tar xf suse10.1_install.tar
 </pre>  </pre>
 <p>  <p>
 This creates a directory named <tt>installation</tt>.  Change to it and  This creates a directory named <tt>installation</tt>.  Change to it and
Line 191  for it to function at all.  Below is a l Line 200  for it to function at all.  Below is a l
 To configure and install LON-CAPA, execute the following commands:  To configure and install LON-CAPA, execute the following commands:
 </p>  </p>
 <pre>  <pre>
 cd /root/loncapa-N.N.N     (N.N.N should correspond to a version number like '2.2.2')  cd /root/loncapa-N.N     (N.N should correspond to a version number like '2.2.2')
 ./UPDATE  ./UPDATE
 </pre>  </pre>
 <p>  <p>
 You will need to enter the LON-CAPA configuration information you determined   You will need to enter the LON-CAPA configuration information you determined 
 in the previous section.    in the previous section.  
 </p>  </p>
 <p>After installing LON-CAPA, and taking any actions included in the WARNINGS file created during installation, it is recommended that you set loncontrol to start automatically on boot, by executing the following command:</p>  
 <pre>  
 /sbin/chkconfig --level 345 loncontrol on  
 </pre>  
 <h2>Creating a Domain Coordinator</h2>  <h2>Creating a Domain Coordinator</h2>
 <p>  <p>
 You will need at least one user at your site who has the role of  You will need at least one user at your site who has the role of
Line 220  perl make_domain_coordinator.pl USERNAME Line 225  perl make_domain_coordinator.pl USERNAME
 <h2>Start/Restart Services</h2>  <h2>Start/Restart Services</h2>
 <p>  <p>
 The LON-CAPA network services take a moment to start.  Most misconfigurations  The LON-CAPA network services take a moment to start.  Most misconfigurations
 will be apparent at this step.  will be appearant at this step.
 </p>  </p>
 <pre>  <pre>
 /etc/init.d/loncontrol start  /etc/init.d/loncontrol start
 /etc/init.d/apache2 start  /etc/init.d/apache start
 </pre>  </pre>
 <p>  <p>
 If you receive warnings when starting the httpd about missing perl modules,  If you receive warnings when starting the httpd about missing perl modules,

Removed from v.1.1  
changed lines
  Added in v.1.2


FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>