Document identifier: | LCG-02-GIS-0002 |
---|---|
Date: | July 20, 2004 |
Author: | Jose Gabadinho, Emanuele Leonardi, Antonio Retico, Alessandro Usai, |
For example, if you are running at CERN the file /etc/sysconfig/network should contain the following line:
HOSTNAME="<LCFGngserverHostName>.cern.ch"
A general requirement for the LCFGng server is to be synchronized to the
other nodes in the farm.
This requirement may be fulfilled in several ways.
If your nodes run under afs, most likely they will be already synchronized. Otherwise, you can use the NTP protocol with a time server. Instructions and examples for a NTP client configuration can be found in [2].
> /sbin/chkconfig --level 2345 sshd on > /sbin/service sshd start
Three packages have to be manually installed in order to start-up the complete set up of the LCFGng server.
> wget http://grid-deployment.web.cern.ch/grid-deployment/download \ /RpmDir/LCFGng/edg-populate-serverng-1.0.23-edg1.noarch.rpm > wget http://grid-deployment.web.cern.ch/grid-deployment/download \ /RpmDir/LCFGng/edg-updaterep-2.0.9-edg1.noarch.rpm > wget http://grid-deployment.web.cern.ch/grid-deployment/download \ /RpmDir/LCFGng/updaterpms-static-server-1.0.2-1.i386.rpm
> rpm -ihv updaterpms-static-server-1.0.2-1.i386.rpm \ edg-updaterep-2.0.9-edg1.noarch.rpm \ edg-populate-serverng-1.0.23-edg1.noarch.rpm
Files needed for LCG releases are available from a CVS server at CERN. This
CVS server contains the list of rpms to install and the LCFGng configuration
files for each node type. Furthermore, in the release, also templates of
site-specific configuration files ( cfgdir-cfg.h,
local-cfg.h , site-cfg.h , and private-cfg.h ) are
provided.
The CVS archive can be reached directly from the LCG Deployment homepage
http://www.cern.ch/grid-deployment
You can follow the CVS Deployment link on the left and then browse
into the repository.
The CVS area where the installation tools and documentation are kept is called
lcg2 .
WARNING: at the same location there is another directory called
lcg-release : this area is used for the integration and certification software, NOT for production. Just ignore it!
Documentation about access to this CVS repository can be found in
[1].
Set the CVSROOT and then check out the software release(s) you want on your
server.
For a single tag you can use
> cvs checkout -r <CURRENT\_TAG> -d <TAG\_DIRECTORY> lcg2A good candidate for TAG_DIRECTORY is for example CURRENT_TAG.
As the client nodes need to "see" the rpm lists, the content of the
rpmlist subdirectory must be copied to
/opt/local/linux/7.3/rpmcfg on the LCFG server: this directory is then
NFS mounted by all client nodes and it is visible as
/export/local/linux/7.3/rpmcfg
Once the rpms lists and LCFGng configuration files for all the node types are
present, the corresponding rpms needed for the wanted release can be downloaded
and installed using the updaterep object.
In TAG_DIRECTORY/tools two configuration files for this script
can be found:
> cp <TAG_DIRECTORY>/tools/updaterep.conf /etc/ > updaterep -vBy default all rpms will be copied to the /opt/local/linux/7.3/RPMS area, that is visible from the client nodes as /export/local/linux/7.3/RPMS.
http://markusw.home.cern.ch/markusw/lcg2CAlist.html
and follow the relevant links to update all the CA-related settings.
Changes and updates of these settings will be announced on the LCG-Rollout
mailing list.
To make sure that all the needed object rpms are installed on your LCFG server,
you should use the lcfgng_server_update.pl script, also located in
TAG_DIRECTORY/tools . This script will report which rpms are
missing or have the wrong version and will create the
/tmp/lcfgng_server_update_script.sh script which you can then use to
fix the server configuration.
/opt/local/linux/nginstallroot/7.3/etc/installparams
The default installparams file assumes the US keyboard and the
CET time zone.
You can use the default values provided by executing:
Installation/upgrade of server packages
> lcfgng_server_update.pl <TAG_DIRECTORY>/rpmlist/lcfgng-common-rpm.h
> /tmp/lcfgng_server_update_script.sh
> lcfgng_server_update.pl <TAG_DIRECTORY>/rpmlist/lcfgng-server-rpm.h
> /tmp/lcfgng_server_update_script.sh
\end {verbatim}
WARNING: please always check the script
\em /tmp/lcfgng\_server\_update\_script.sh \em verifing that all the rpm
update commands look reasonable before running it.\\\\
The script \em /tmp/lcfgng\_server\_update\_script.sh \em may encounter
some problems with missing dependencies. Usually they are not critical
and they are due to the fact that the script launches independent rpm
statements. Since dependencies are supposed to have been checked before,
an easy way to proceed is to run again the script until no more missing
dependencies exist.
\end{itemize}
\section{Build LiveOS}
The LiveOS is the Operative system to be mounted by client nodes during the
initial boot phase and will be used to steer the whole node installation.\\
In order to install the LiveOS on the LCFGng server, you can use the released
script\\
\em $<$TAG\_DIRECTORY$>$/tools/lcfgng\_installroot.pl \em.\\\\
This script uses configuration parameters read from the file
\em lcfgng\_installroot.cfg\em, which must be in perl format.\\
What follows is a list of the configurable actions done by the script:
\begin{itemize}
\item Set the root directory where all LiveOS versions will be installed
(default: \em /opt/local/linux/nginstallroot\em).\\
Notice that this directory needs to be created explicitly!.
\item Create the file containing the list of RPMs to install on the LiveOS
(the default list is the \em LIVEOS-rpm\em, that should be part of the
release itself. It's not recommended to change it).
\item Set the directory where the rpm lists reside (default:
\em /opt/local/linux/$<$RH-version$>$/rpmcfg \em)
\item Set the path of the rpm command to use (def: \em /bin/rpm\em)
\end{itemize}
The required steps to install and configure the LiveOS on a LCFGng server
are outlined below:
\begin{itemize}
\item Install the LiveOS on the LCFGng server
\begin{verbatim}
> cd <TAG_DIRECTORY>/tools
> lcfgng_installroot.pl
WARNING: The script lcfgng_installroot.pl must be launched
within the TAG_DIRECTORY/tools directory so that its
configuration file can be found.
It is advisable to save the output into a log file as the output size
is considerable.
In order to set up local installation parameters (e.g. keyboard,
time zone) edit the file
> cd /opt/local/linux/nginstallroot/7.3/etc
> cp installparams.default installparams
If you want to use a different set of defaults, you should edit the
installparams file.
Set up LCFGng Interface Services (DHCP, WEB and NFS servers)