-
Notifications
You must be signed in to change notification settings - Fork 21
ESGF Installation Using Autoinstaller
Regardless of whether you have installed and administered an ESGF node previously, please read the following document on ESGF policies, as this should influence what type on installation you should do:
http://esgf.llnl.gov/media/pdf/ESGF-Policies-and-Guidelines-V1.0.pdf
The ESGF Autoinstaller provides a full installation on a clean linux system without the need to answer questions during the course of the installation. This procedure assumes either (1) installation of all four ESGF node subtypes: Data, Index, IDP, Compute; or (2) a Data-only node. If you desire to install some other combination of the subtypes, e.g. index and IDP, please perform a traditional installation without the aid of the Autoinstaller.
We have migrated the ESGF installation procedure to use Ansible. Please see the following:
Information on the use of esgf-installer scripts are below, though maintenance of these scripts have been discontinued on April 1, 2019.
Currently, there is no devel release of ESGF available. Please install 2.8.2 master instead.
2.8.2-master-release
- RHEL 6, CentOS 6, Scientific Linux 6
- You must be root or effectively root to run this program, prefixing the command with sudo will not allow the use of needed environment variables! If you must use sudo, do so only to become root, using sudo su -.
- Ports to open: 80, 443, (GridFTP: 2811, 50000-51000), (MyProxy: 7512)
- The Expect command is required to use the autoinstaller. Expect can be installed using
yum install expect - During the installation process, you'll be asked for a globus username and password. You'll need to sign up for a globusonline account beforehand, and provide the username and password when asked for it. You can sign up for an account at https://www.globus.org/SignUp
To setup a 'devel' install
cd /usr/local/bin
wget -O esg-bootstrap http://distrib-coffee.ipsl.jussieu.fr/pub/esgf/dist/devel/2.8/0/esgf-installer/esg-bootstrap --no-check-certificate
chmod 555 esg-bootstrap
./esg-bootstrap --devel
To setup a 'master' install
cd /usr/local/bin
wget -O esg-bootstrap http://distrib-coffee.ipsl.jussieu.fr/pub/esgf/dist/2.8/2/esgf-installer/esg-bootstrap --no-check-certificate
chmod 555 esg-bootstrap
./esg-bootstrap
Start the auto-installer process
The autoinstaller consists of two files, esg-autoinstall and esg-autoinstall.conf. The esg-autoinstall file uses Expect to glean configuration answers from the esg-autoinstall.conf file.
When the bootstrap is run, the esg-autoinstall script gets placed at /usr/local/bin and the esg-autoinstall.conf file gets placed at /usr/local/etc.
- Edit the
esg-autoinstall.conffile with your node's configuration options. See release specific questions below. Additionally check the expect script.
--> THIS STEP IS IMPORTANT! Make sure you at least review all questions in the .conf file. For THREDDS, this should be Y for new installations, else N. For custom/advance configurations it is suggested that you review all questions. - Run the
esg-autoinstallscript. You could save a transcript of the installation, if you run it so:
script -c '/usr/local/bin/esg-autoinstall' installation.log
** MAKE SURE you back up the esg-autoinstall.conf file for future use. The bootstrapper will overwrite this file with the default settings ***
** Additional notes **
-
If you plan to publish CMIP6 data make sure you answer Y to the question regarding that (not a default).
-
Tier 1 IDP only - We encourage all sites to deploy the SLCS service so please answer Y.
For self-generated certificates, install them like this:
(Note: Do not worry about warnings/errors during the node stop)
./esg-node stop
./esg-node --install-keypair /etc/tempcerts/hostcert.pem /etc/tempcerts/hostkey.pem
For the CA chain question, use /etc/tempcerts/cacert.pem
./esg-node start
If you have signed certificates, use those instead:
./esg-node stop
./esg-node --install-local-certs
./esg-node --install-keypair /etc/esgfcerts/hostcert.pem /etc/esgfcerts/hostkey.pem
If your certificates were signed by:
The IPSL CA, use /etc/grid-security/certificates/0597e90c.0.
The NSC CA, use /etc/grid-security/certificates/cd6ccc41.0.
The ANL CA, use /etc/grid-security/certificates/99eb76fc.0.
When prompted, restart the node with ./esg-node restart.