Return to RHEL7_install.frag CVS log

Up to [LON-CAPA] / doc / build

Installation instructions for RHEL7.

    1: <h1>Installing LON-CAPA on a minimal Red Hat Enterprise Linux 7 System</h1>
    2: <p>
    3: This document guides you through the process of setting up a new LON-CAPA
    4: server running Red Hat Enterprise Linux 7 with a minimum of packages installed.
    5: The computer will be configured solely as a LON-CAPA server and will be
    6: expected to have no other services running.  Your server is expected to have
    7: a reasonably fast connection to the internet.
    8: </p><p>
    9: More information is available at
   10: <a href="http://install.lon-capa.org/">http://install.lon-capa.org/</a>.
   11: </p>
   12: 
   13: <h2>Before you begin</h2>
   14: <p>
   15: Installing Linux is getting easier and easier.
   16: You will be required to log in to the machine and execute
   17: some routine Unix commands.  Familiarity with the Apache web server, mod_perl,
   18: perl, and MySQL are not required to install and run LON-CAPA.
   19: </p>
   20: 
   21: <h2>Installation Overview</h2>
   22: <p>
   23: The installation process takes the following steps:
   24: </p>
   25: <ol>
   26:   <li><a href="#obt">Obtain Red Hat Enterprise Linux 7 installation iso file or media</a></li>
   27:   <li><a href="#net">Determine Network Settings</a></li>
   28:   <li><a href="#lin">Install Red Hat Enterprise Linux 7</a></li>
   29:   <li><a href="#upd">Update your system</a></li>
   30:   <li><a href="#ilc">Install LON-CAPA</a></li>
   31:   <li><a href="#cdc">Create a Domain Coordinator</a></li>
   32:   <li><a href="#sts">Start/Restart services</a></li>
   33:   <li><a href="#log">Log in to LON-CAPA</a></li>
   34: </ol>
   35: 
   36: <hr>
   37: <h2>1. <a name="obt">Obtain Red Hat Enterprise Linux 7</a></h2>
   38: <p>
   39: RHEL7 downloads are available from Red Hat:
   40: <a href="http://redhat.com/">http://redhat.com/</a>.
   41: Either download the Boot ISO or the RHEL 7 binary
   42: </p>
   43: 
   44: <h2>2. <a name="net">Determine Network Settings</a></h2>
   45: <p>
   46: You will need to know the following network settings for your installation.
   47: <b>Note:</b>You must have a static IP address to use LON-CAPA.
   48: DHCP is <em>not</em> supported.
   49: 
   50: <ul>
   51:   <li>ip address </li>
   52:   <li>netmask </li>
   53:   <li>hostname </li>
   54:   <li>gateway </li>
   55:   <li>domain name server(s) </li>
   56: </ul>
   57: 
   58: <h2>3. <a name="lin">Minimal  Red Hat Enterprise Linux 7c Install</a></h2>
   59: <p>
   60: Installing Red Hat Enterprise Linux is straightforward. 
   61: Documentation is available from
   62: <a href="https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/"
   63: https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/</a>
   64: Most of the installation screens are self explanatory.
   65: There are a few steps that require comment and are dealt with below.
   66: </p>
   67: <dl style="list-style:square outside none">
   68:    <dt>Installation Language</dt>
   69:    <dd>Use English as your installation language.</dd>
   70:    <dt>Installation Destination</dt>
   71:    <dd>For a fresh install may want to use the automatic partitioning feature of the installer.
   72:        If you want to customize partitioning check the "I will configure partitioning" radio button.
   73:        LON-CAPA resource files are stored in the /home directory, so the
   74:        majority of the disk space should be allocated here.  If you have 20 GB
   75:        of space for RHEL, /home should receive at least 10 to 12 GB.
   76:        Since Mariadb uses the /var filesystem to store its databases you should
   77:        have at least 4 GB of space available on /var.  Be sure to
   78:        include adequate swap space.  A minimum is 512 MB, but you should
   79:        typically have 1 or 2x as much swap space as you do physical RAM.</dd>
   80:    <dt>Network and Hostname</dt>
   81:    <dd>LON-CAPA will <b>not</b> work with a machine set up to use a dynamic
   82:        IP address.  When configuring your network card, be sure to unselect
   83:        the DHCP option and enter your network information. Enter your hostname</dd>
   84:    <dt>Software Selection</dt>
   85:    <dd>Select the "Minimal Install" radio button.</dd>
   86: </dl>
   87: <p>
   88: Finish installing your server, reboot it, and log in as root.
   89: </p>
   90: <h3>Firewall Configuration</h3>
   91: <p>
   92: LON-CAPA uses the tradition iptables package instead of the recent Firewalld, included for the
   93: first time with RHEL7.  Accordingly, you should install iptables-services, disable firewalld,
   94: and enable iptables.  
   95: <pre>
   96: yum install iptables-services
   97: systemctl mask firewalld
   98: systemctl enable iptables
   99: systemctl enable ip6tables
  100: yum install wget
  101: rpm --import http://install.loncapa.org/versions/redhat/RPM-GPG-KEY-loncapa
  102: wget http://install.loncapa.org/versions/redhat/7Server/system-config-firewall-tui-1.2.29-10.el7.noarch.rpm
  103: yum localinstall system-config-firewall-tui-1.2.29-10.el7.noarch.rpm
  104: system-config-firewall-tui
  105: </pre>
  106: 
  107: The system-config-firewall-tui tool should be used to configure the Firewall.
  108: </p>
  109: <ol>
  110:   <li>Select Security Level: Enabled, and Customize, to allow
  111:       incoming: SSH (remote login), WWW (HTTP) and secure WWW
  112:       (HTTPS).
  113:   </li>
  114:   <li>Select OK, and then Quit</li>
  115: </ol>
  116: 
  117: <h2>4. <a name="upd">Update your system</a></h2>
  118: <p>
  119: Update your system to the latest versions of the system software using yum.
  120: </p>
  121: <pre>
  122: yum update
  123: </pre>
  124: <p>
  125: Reboot your system before continuing with the installation.
  126: </p>
  127: <p>
  128: Retrieve the rhel7_loncapa_yum file from the LON-CAPA install site:
  129: </p>
  130: <pre>
  131: wget http://install.loncapa.org/versions/redhat/7Server/rhel7_loncapa_yum.conf
  132: </pre>
  133: <p>
  134: Install the rhel7_loncapa_yum.conf
  135: </p>
  136: <pre>
  137: mv /etc/yum.conf /etc/yum.conf.backup
  138: cp rhel7_loncapa_yum.conf /etc/yum.conf
  139: yum update
  140: </pre>
  141: 
  142: <h3>Configure SELinux</h3>
  143: <p>
  144: The default RHEL7 installation includes SELinux enabled. Until such time as an SELinux security policy has been created for LON-CAPA, SELinux should be disabled.
  145: Retrieve the loncapa_selinux_config file from the LON-CAPA install site:
  146: </p>
  147: <pre>
  148: wget http://install.loncapa.org/versions/redhat/7Server/loncapa_selinux_config
  149: </pre>
  150: <p>
  151: Install the selinux config file
  152: </p>
  153: <pre>
  154: mv /etc/selinux/config /etc/selinux/config.backup
  155: mv loncapa_selinux_config /etc/selinux/config
  156: reboot
  157: </pre>
  158: 
  159: <h2>5. <a name="ilc">Installing LON-CAPA</a></h2>
  160: <h3>Install prerequisites</h3>
  161: <p> Execute: </p>
  162: <pre>
  163: yum install LONCAPA-prerequisites
  164: </pre><p>
  165: This may take some minutes due to LON-CAPA's large number of dependencies.
  166: </p>
  167: <h3>Retrieve and execute LON-CAPA setup program</h3>
  168: <p>
  169: Retrieve the LON-CAPA setup with the following command:
  170: </p>
  171: <pre>
  172: wget http://install.loncapa.org/linux/install.tar
  173: </pre>
  174: <p>
  175: Extract the archive with the following command:
  176: </p>
  177: <pre>
  178: tar xf install.tar
  179: </pre>
  180: <p>
  181: This creates a directory named <tt>installation</tt>.  Change to it and
  182: execute the setup script with the following commands:
  183: </p>
  184: <pre>
  185: cd installation
  186: ./install.pl
  187: </pre>
  188: <p>
  189: The script is used to prepare a Linux system to run LON-CAPA, and can also be
  190: used to check the configuration of a system on which LON-CAPA has already been installed.  Typically, though, you will run this script only once, when you first install LON-CAPA.
  191: </p>
  192: <p>
  193: The script will analyze your system to determine which actions are recommended.  The script will then prompt you to choose the actions you would like taken.
  194: Once a choice has been entered for all nine possible actions, required changes will be made.
  195: </p>
  196: <p>The possible actions are:</p>
  197: <ul>
  198: <li>Create the www user/group</li>
  199: <li>Install the package LON-CAPA uses to authenticate users.</li>
  200: <li>Set-up the MySQL (Mariadb) database</li>
  201: <li>Set-up MySQL (Mariadb) permissions</li>
  202: <li>Configure Apache web server</li>
  203: <li>Configure start-up of services</li>
  204: <li>Check firewall settings</li>
  205: <li>Stop services not used by LON-CAPA,  e.g., services for a print server: cups daemon</li> 
  206: <li>Download LON-CAPA source code in readiness for installation</li>
  207: </ul>
  208: <h3>Determine LON-CAPA Settings</h3>
  209: <p>
  210: LON-CAPA requires a number of identifying parameters to be set in order
  211: for it to function at all.  Below is a list with descriptions.
  212: </p>
  213: <dl>
  214:   <dt>Host Type (library or access)</dt>
  215:   <dd>The server must be designated a 'library' or an 'access' server.  In
  216:       general you should have a library server for your instructors to create
  217:       their course content on and run their courses.  Students should connect
  218:       to access servers.  If you are doing the first install of LON-CAPA at
  219:       your site, or if you are playing with it for your own edification you
  220:       should make your machine a 'library' server.</dd>
  221:   <dt>LON-CAPA domain</dt>
  222:   <dd>Each site or school which installs LON-CAPA needs its own domain.
  223:       Here at MSU we use 'msu'.  You should choose something short but
  224:       meaningful.  <i>Restriction: One word, no hyphens, underscores, or
  225:       special characters.</i><br>Domain names which include a departmental
  226:       abbreviation are not recommended as although LON-CAPA may start in
  227:       a single department, other departments frequently join subsequently.
  228:       For a domain name: 'msu' is a superior choice to 'msuphys' for example.
  229:   </dd>
  230:   <dt>LON-CAPA host id</dt>
  231:   <dd>Each LON-CAPA server requires a unique internal name.  We use names
  232:       such as "msul1" for the first library server. <i>Restriction: One word,
  233:       no hyphens, underscores, or special characters.</i>
  234:   </dd>
  235:   <dt>Domain's Primary Library Server ID</dt>
  236:    <dd>If you are setting up a domain with a single library server, then the domain's primary library server ID will be the LON-CAPA host id of that server (e.g., msul1). Once your domain grows and you need to add more servers, one of the library servers in the domain should be assigned as the domain's primary library server.  This will be where domain-wide settings will be stored.<dd>
  237:   <dt>Host administrator email</dt>
  238:   <dd>The amount of email sent to this address is relatively minimal.  Messages
  239:       are sent every time the system starts up, or if the system is in
  240:       serious trouble. On a laptop, make this <tt>root@localhost</tt>.
  241:   </dd>
  242:   <dt>Support email address</dt>
  243:   <dd>If you enter an e-mail address here, then users of the system
  244:       will be able to click an "Ask Helpdesk" link in the system to
  245:       display a web form which they will complete to request support from
  246:       your institution's helpdesk. On form submission the contents
  247:       will be sent to the e-mail address you specify.
  248:   </dd>
  249: </dl>
  250: 
  251: <h3>Configuring LON-CAPA</h3>
  252: <p>
  253: To configure and install LON-CAPA, execute the following commands:
  254: </p>
  255: <pre>
  256: cd /root/loncapa-X.Y.Z     (X.Y.Z should correspond to a version number like '2.11.0')
  257: ./UPDATE
  258: </pre>
  259: <p>
  260: You will need to enter the LON-CAPA configuration information you determined
  261: in the previous section.
  262: </p>
  263: 
  264: <h2>6. <a name="cdc">Creating a Domain Coordinator</a></h2>
  265: <p>
  266: You will need at least one user at your site who has the role of
  267: 'domain coordinator'.  This user creates accounts for other users and
  268: grants them additional privileges.  The make_domain_coordinator.pl script
  269: invoked below requires that you enter the user's password. 
  270: Feel free to use the "passwd username" command to change it later. 
  271: Replace USERNAME and DOMAIN with an appropriate user name and your domain.
  272: If installing a library server and an access server on separate machines or VMs
  273: you need only run make_domain_coordinator.pl on the library server. 
  274: </p>
  275: <pre>
  276: cd /root/loncapa-X.Y.Z/loncom/build
  277: perl make_domain_coordinator.pl USERNAME DOMAIN
  278: </pre>
  279: 
  280: <h2>7. <a name="sts">Start/Restart Services</a></h2>
  281: <p>
  282: The LON-CAPA network services take a moment to start.  Most misconfigurations
  283: will be apparent at this step.
  284: </p>
  285: <pre>
  286: /etc/init.d/loncontrol start
  287: service httpd start
  288: </pre>
  289: <p>
  290: If you receive warnings about missing perl modules, when starting the httpd service
  291: please make sure you followed the instructions in
  292: <b>Installing LON-CAPA Dependencies</b>.  If you still have errors, please
  293: contact the LON-CAPA Helpdesk -- helpdesk at loncapa.org
  294: </p>
  295: 
  296: <h2>8. <a name="log">Log in to your LON-CAPA Machine</a></h2>
  297: <p>
  298: Point a web browser at your new machine and log in as the domain
  299: coordinator.  Congratulations!
  300: </p>
  301: 
  302: <hr>
  303: <h2>If things aren't working right</h2>
  304: <p>
  305: If you've followed the steps above and the server doesn't start or you think
  306: there's something wrong, please contact the LON-CAPA helpdesk. 
  307: Installation/update support is available from:  helpdesk at loncapa.org  
  308: (replace " at " with @).
  309: If there were errors in installation of the dependency RPMs or errors during the
  310: automatic setup, please send us as much information as possible.
  311: If some part of this document is unclear please let us know.
  312: </p>