Forskjell mellom versjoner av «Computing System Administration»
Linje 107: | Linje 107: | ||
[https://lcg-voms.cern.ch:8443/vo/atlas/vomrs?path=/RootNode&action=execute This site] is used for registering atlas VO grid resource users and for managing information about their affiliation with the ATLAS VO and their permissions regarding use of grid resources.<br> | [https://lcg-voms.cern.ch:8443/vo/atlas/vomrs?path=/RootNode&action=execute This site] is used for registering atlas VO grid resource users and for managing information about their affiliation with the ATLAS VO and their permissions regarding use of grid resources.<br> | ||
+ | |||
+ | === Setting up VOMS for US ATLAS certificates === | ||
+ | |||
+ | Create a file | ||
+ | <pre>/ | ||
+ | etc/grid-security/vomsdir/atlas/vo.racf.bnl.gov.lsc | ||
+ | </pre> | ||
+ | The file currently needs to be named | ||
+ | <pre> | ||
+ | /etc/grid-security/vomsdir/atlas/vo02.racf.bnl.gov.lsc | ||
+ | </pre> | ||
+ | The file name is determined from the output of "voms-proxy-info -uri": | ||
+ | |||
+ | That is due to a misconfiguration of the BNL VOMS server. | ||
+ | The admins have been informed (10.03.10). Better create _both_ files for now. | ||
+ | |||
+ | The contents: | ||
+ | <pre> | ||
+ | /DC=org/DC=doegrids/OU=Services/CN=vo.racf.bnl.gov | ||
+ | /DC=org/DC=DOEGrids/OU=Certificate Authorities/CN=DOEGrids CA 1 | ||
+ | </pre> | ||
+ | |||
+ | Then you can stop bothering with the certificate (which should be in lcg-vomscerts and which expires once a year). | ||
=== Installation of a new release of DQ2Clients === | === Installation of a new release of DQ2Clients === |
Revisjonen fra 10. mar. 2010 kl. 11:44
Innhold
- 1 Getting ATLAS releases to work on RHEL5 x86_64 nodes
- 2 Getting the I686-SLC5-GCC43 kits to validate (and run) on RHEL5
- 3 Installing root and enabling the xrootd service (needed for proof)
- 4 Installing VirtualBox
- 5 Installing ARC client on RHEL5 boxes (as superuser)
- 6 Installing an ATLAS software release (NEW 03.02.2010)
- 7 ATLAS VO Registration and Management
- 8 Setting up VOMS for US ATLAS certificates
- 9 Installation of a new release of DQ2Clients
- 10 Getting COMPHEP to work on 64-bit RHEL5
Getting ATLAS releases to work on RHEL5 x86_64 nodes
- For pacman to work you need to install an older 32-bit opensll: rpm -ivh http://ftp.scientificlinux.org/linux/scientific/51/i386/SL/openssl097a-0.9.7a-9.i386.rpm
- To satisfy some packages, especially event generation: yum install libgfortran-4.1.2-44.el5.i386
- You need to install blas: yum install blas.i386 and yum install blas-devel.i386
- To get /usr/lib/libreadline.so.4 (also needed for 32-bit Linux) do rpm -ivh http://linuxsoft.cern.ch/cern/slc5X/i386/SL/compat-readline43-4.3-3.i386.rpm
- You need 32-bit gcc 3.4 (also needed for 32-bit Linux): yum install compat-gcc-34
- You need 32-bit g++ 3.4 (also needed for 32-bit Linux): yum install compat-gcc-34-c++
- You may need to install 32-bit popt: yum install popt.i386
- In order to analyze luminosity blocks in real data libxml2-devel is needed: yum install libxml2-devel
Getting the I686-SLC5-GCC43 kits to validate (and run) on RHEL5
- Install the pacman kit for gcc43, see https://twiki.cern.ch/twiki/bin/view/Atlas/RPMCompatSLC5#Run_SLC4_32bit_binaries_on_SLC5
- You probably need to ln -s /usr/lib/libg2c.so.0.0.0 /usr/lib/libg2c.so
- You probably need to ln -s /usr/lib/gcc/x86_64-redhat-linux/3.4.6/libgcc_s_32.so /lib/libgcc_s_32.so
Installing root and enabling the xrootd service (needed for proof)
- on RHEL5 x86_64 systems: (gcc 4.3 is too advanced for UiO desktops)
tar -xvzf /mn/kvant/hep/linux/root/root_v5.22.00.Linux-slc5-gcc3.4.tar.gz -C /opt
- Assume standard setup is on default system (e.g. scalar.uio.no) and $node is the node you want to install on. Of course if you are logged on to $node all the ssh'ing is not needed
scp /etc/sysconfig/xrootd $node:/etc/sysconfig/ scp /etc/xpd.cf $node:/etc/ scp /etc/rc.d/init.d/xrootd $node:/etc/rc.d/init.d/ ssh $node chkconfig --add xrootd ssh $node chkconfig --level 35 xrootd on
- Note, xrootd runs under read account (as of May 2009)
ssh $node mkdir /var/log/xrootd ssh $node chown read:fysepf /var/log/xrootd
- Edit /etc/xpd.cf and restart xrootd to add a worker node.
- Redistribute /etc/cpd.cf as well (have to find a simpler but reliable system for this
/sbin/service xrootd start
Installing VirtualBox
- Download and install the appropriate rpm from http://download.virtualbox.org/virtualbox
- Remove the new line with vboxusers from /etc/group
- Add the host's username to the vboxusers group, e.g.
echo vboxusers:x:15522:esbenlu >> /etc/group<br>echo vboxusers:x:15522:esbenlu >> /etc/group.local
- Finalize the vbox setup:
/etc/init.d/vboxdrv setup
Installing ARC client on RHEL5 boxes (as superuser)
- See http://download.nordugrid.org/repos.html
- Set up the extra packages for Enterprise Linux (epel):
rpm -ivh ftp://fr.rpmfind.net/linux/EPEL/5/`uname -i`/epel-release-5-3.noarch.rpm
- Typical /etc/yum.repos.d/nordugrid:
[nordugrid] name=NorduGrid - $basearch - stable baseurl=http://download.nordugrid.org/repos/redhat/$releasever/$basearch/stable enabled=1 gpgcheck=1 gpgkey=http://download.nordugrid.org/RPM-GPG-KEY-nordugrid;
- yum groupinstall "ARC Client" to install the client s/w
- yum install nordugrid-arc-ca-utils to install the missing Certificate Authority utilities
- /opt/nordugrid/sbin/grid-update-crls to jumpstart the first update of the Certificate Revocation Lists - after that there is a cron that does the job automatically.
Installing an ATLAS software release (NEW 03.02.2010)
- Decide where to install the software - this is "swdir".
- Decide where to install the runtime scripts, this is "rtedir".
- Download the install scripts and chmod a+x them afterwards
- Install an appropriate gcc432 compiler (use "uname -m" to find yours). You can't use the i686 gcc-kit on a x86_64 system! When installed in this way the atlas release(s) you install later will refer to them implicitly - you shouldn't need to source them yourself unless you are doing non-atlas program development. Note that SLC4 is no longer the default platform and will soon be discontinued (though if you must have older releases you will find SLC4 kits).
- ./AtlasInstall.sh --release 4.3.2 --project gcc --arch I686-SLC5-GCC43-OPT --rtedir /my/runtime --swdir /my/atlas/software
- ./AtlasInstall.sh --release 4.3.2 --project gcc --arch X86_64-SLC5-GCC43-OPT --rtedir /my/runtime --swdir /my/atlas/software
- ./AtlasInstall.sh with no arguments will give you help.
- Install the kit you want (x86_64 kits are not yet validated for physics). The i686 kit will work on both i686 and x86_64 systems. Beware that the DBRelease needs to be modern enough. Check the release notes for your release in http://atlas-computing.web.cern.ch/atlas-computing/projects/releases/status/ (and be warned, these pages are written by hand and the DBRelease is often wrong).
- Example: ./AtlasInstall.sh --release 15.6.3 --project AtlasOffline --arch I686-SLC5-GCC43-OPT --rtedir /my/runtime --swdir /my/atlas/software --dbrelease 8.5.1
- If you need a production cache the next step is:
- ./AtlasInstall.sh --release 15.6.3 --project AtlasOffline --arch I686-SLC5-GCC43-OPT --rtedir /my/runtime --swdir /my/atlas/software --dbrelease 8.5.1
- If you want a Tier0 cache instead just change the project to AtlasTier0.
- If your OS is x86_64 there may be some missing 32-bit libraries, my "favorites" are from the blas, blas-devel, libgfortran and libf2c packages. See Computing_System_Administration#Getting_ATLAS_releases_to_work_on_RHEL5_x86_64_nodes and the ATLAS wiki for more details.
ATLAS VO Registration and Management
This site is used for registering atlas VO grid resource users and for managing information about their affiliation with the ATLAS VO and their permissions regarding use of grid resources.
Setting up VOMS for US ATLAS certificates
Create a file
/ etc/grid-security/vomsdir/atlas/vo.racf.bnl.gov.lsc
The file currently needs to be named
/etc/grid-security/vomsdir/atlas/vo02.racf.bnl.gov.lsc
The file name is determined from the output of "voms-proxy-info -uri":
That is due to a misconfiguration of the BNL VOMS server. The admins have been informed (10.03.10). Better create _both_ files for now.
The contents:
/DC=org/DC=doegrids/OU=Services/CN=vo.racf.bnl.gov /DC=org/DC=DOEGrids/OU=Certificate Authorities/CN=DOEGrids CA 1
Then you can stop bothering with the certificate (which should be in lcg-vomscerts and which expires once a year).
Installation of a new release of DQ2Clients
- You had better set umask to 022 or nobody else will be able to read files or execute any commands!
- Typical install command is
pacman -trust-all-caches -allow tar-overwrite -get http://atlas.web.cern.ch/Atlas/GROUPS/DATABASE/project/ddm/releases/pacman/cache:DQ2Clients
Getting COMPHEP to work on 64-bit RHEL5
yum install compat-gcc-34-g77 g2clib-devel cd /usr/lib64;ln -s libg2c.so.0.0.0 libg2c.so
The latter assumes that a similar fix for /usr/lib (32-bit) has already been done (see above).