This page describes the necessary steps for installing of dl160

On the server

Install external packages

As root:

  • create yum repository definitions (do not enable them):

    # atrpms
    echo '[atrpms]' > /etc/yum.repos.d/atrpms.repo
    echo 'name=name=CentOS $releasever - $basearch - ATrpms' >> /etc/yum.repos.d/atrpms.repo
    echo 'baseurl=$releasever-$basearch/atrpms/stable' >> /etc/yum.repos.d/atrpms.repo
    echo '#baseurl=$releasever-$basearch/atrpms/stable' >> /etc/yum.repos.d/atrpms.repo
    echo 'gpgkey=' >> /etc/yum.repos.d/atrpms.repo
    echo 'gpgcheck=1' >> /etc/yum.repos.d/atrpms.repo
    echo 'enabled=0' >> /etc/yum.repos.d/atrpms.repo
    # epel
    echo '[epel]' > /etc/yum.repos.d/epel.repo
    echo 'name=name=CentOS $releasever - $basearch - EPEL' >> /etc/yum.repos.d/epel.repo
    echo 'baseurl=$releasever/$basearch' >> /etc/yum.repos.d/epel.repo
    echo 'gpgkey=' >> /etc/yum.repos.d/epel.repo
    echo 'gpgcheck=1' >> /etc/yum.repos.d/epel.repo
    echo 'enabled=0' >> /etc/yum.repos.d/epel.repo
  • install:

    yum install yum-utils
  • configure rpmbuild:

    • use the following ~rpmbuild/.rpmmacros:

      %disttag        el5.fys
      %distribution   Fysik RPMS
      %vendor         Fysik RPMS <>
      %_signature     gpg
      %_gpg_path      ~/.gnupg
      %_gpg_name      Fysik RPMS
      #%_topdir       /home/camp/rpmbuild/AMD-Opteron
      %_topdir        /home/camp/rpmbuild/Intel-Nehalem
      %_rpmdir        %{_topdir}/RPMS
      %_srcrpmdir     %{_topdir}/SRPMS
      %_svndir        /home/camp/rpmbuild/rpmbuild
      %_specdir       %{_svndir}/SPECS
      %_sourcedir     %{_svndir}/SOURCES
      %_rpmfilename   %%{NAME}-%%{VERSION}-%%{RELEASE}.%%{ARCH}.rpm
      #%_tmppath      %{_topdir}
      %_tmppath       /tmp/rpmbuild
      %_builddir      %{_tmppath}/BUILD
      %niflheim       1
    • as rpmbuild create directories:

      mkdir -p ~/Intel-Nehalem/RPMS
      mkdir -p ~/Intel-Nehalem/SRPMS
      mkdir -p ~/Intel-Nehalem/BUILD
      mkdir -p /tmp/rpmbuild/BUILD
  • install official packages, as rpmbuild:

    cd ~/Intel-Nehalem/RPMS
    yumdownloader --resolve gcc-gfortran gcc43-c++ gcc43-gfortran blas-devel lapack-devel python-devel
    yumdownloader --resolve gnuplot libXi-devel xorg-x11-fonts-100dpi pexpect tetex-latex tkinter qt-devel
    yumdownloader --resolve openmpi openmpi-devel openmpi-libs compat-dapl libibverbs librdmacm openib
    yum localinstall * # as root
  • install atrpms packages, as rpmbuild (vtk-python is currently unavailable 16 Apr 2009):

    yumdownloader --resolve --enablerepo=atrpms vtk-python fftw2 fftw2-devel netcdf netcdf-devel arpack-devel graphviz
    rpm --import RPM-GPG-KEY.atrpms # as root
    yum localinstall * # as root
  • install the packages from epel, as rpmbuild:

    yumdownloader --resolve --enablerepo=epel fftw3 fftw3-devel python-matplotlib python-docutils jmol
    yumdownloader --resolve --enablerepo=epel environment-modules suitesparse-devel
    rpm --import RPM-GPG-KEY-EPEL # as root
    yum localinstall * # as root
    source /etc/profile.d/
  • edit /etc/yum.conf so it contains:

    exclude=netcdf-* netcdf3-* fftw-* fftw2-* fftw3-* python-numeric openmpi-*

It's time to build custom RPMS

As root:

cd ~/rpmbuild/SPECS

Skip this step if not installing on "dulak-server": create the /home/dulak-server/rpm/campos directory (to keep custom built RPMS):

mkdir /home/dulak-server/rpm/campos

Preferably build a custom openmpi, using the latest gcc/gfortran and torque support:

wget \
     -O ~/rpmbuild/SOURCES/openmpi-1.3.1.tar.bz2
export rpmtopdir=${HOME} # set this to _topdir value from ~/.rpmmacros
sh ./ ../SOURCES/openmpi-1.3.1.tar.bz2 2>&1 | tee
rpm -ivh ~/RPMS/*/openmpi-*.rpm
cp ~/RPMS/*/openmpi-*.rpm /home/dulak-server/rpm/campos

If scripts that contain ALL build/install/uninstall commands ( and need to be created, every time after an RPM is successfully built, do:

grep -v "#\!" >> ~/
cat ~/ | grep -v "#\!" >> ~/ && mv -f ~/ ~/
# ignore "cat: /root/ No such ..." error when running first time

Note that won't remove built RPM files, just will uninstall the packages.

Build the following for dacapo:

  • campos-dacapo-pseudopotentials:

    python --machine='dulak-cluster' --create_scripts campos-dacapo-pseudopotentials
  • rasmol:

    python --machine='dulak-cluster' --create_scripts RasMol
    cp ~/RPMS/*/RasMol-*.rpm /home/dulak-server/rpm/campos
  • gnuplot-py:

    python --machine='dulak-cluster' --create_scripts gnuplot-py
    cp ~/RPMS/*/gnuplot-py-*.rpm /home/dulak-server/rpm/campos

    if you use modules:

    module load gnuplot-py
    echo "module load gnuplot-py" >> ~/

    otherwise logout and login again!

  • cblas:

    python --machine='dulak-cluster' --create_scripts cblas
    cp ~/RPMS/*/cblas-*.rpm /home/dulak-server/rpm/campos
  • python-numeric (we must install 24.2 version, and we keep the default version):

    rpm -e --nodeps python-numeric
    yumdownloader --resolve --disableexcludes=main python-numeric
    cp python-numeric-*.rpm /home/dulak-server/rpm/external # **Skip this step if not installing on "dulak-server"**
    cd ~/rpmbuild/SPECS
    python --machine='dulak-cluster' --create_scripts python-numeric
    cp ~/RPMS/*/python-numeric-*.rpm /home/dulak-server/rpm/campos

    Note: (16 Apr 2009) currently Numeric's results in (we ignore this error):

    glibc detected *** python: free(): invalid next size (normal): 0x09aee970 ***

    If you use modules:

    module load python-numeric
    echo "module load python-numeric" >> ~/

    otherwise logout and login again!

    After installing python-numeric make a very rough check:

    python -c "import lapack_lite"
    ldd `rpm -ql python-numeric | grep`
    ldd `rpm -ql python-numeric | grep`

    and reinstall the default version:

    rpm -ivh --oldpackage ~/python-numeric-*.rpm
  • ScientificPython:

    python --machine='dulak-cluster' --create_scripts ScientificPython
    cp ~/RPMS/*/ScientificPython-*.rpm /home/dulak-server/rpm/campos
  • campos-ase2:

    python --machine='dulak-cluster' --create_scripts campos-ase2
    cp ~/RPMS/*/campos-ase2-*.rpm /home/dulak-server/rpm/campos
  • campos-dacapo-python:

    python --machine='dulak-cluster' --create_scripts campos-dacapo-python
  • campos-dacapo:

    python --machine='dulak-cluster' --create_scripts --compiler=gfortran43 campos-dacapo
    cp ~/RPMS/*/campos-dacapo-*.rpm /home/dulak-server/rpm/campos

    logout and login again!

build following for gpaw:

  • campos-gpaw-setups:

    python --machine='dulak-cluster' --create_scripts campos-gpaw-setups
  • campos-ase3:

    python --machine='dulak-cluster' --create_scripts campos-ase3
    cp ~/RPMS/*/campos-ase3-*.rpm /home/dulak-server/rpm/campos
  • campos-gpaw:

    python --machine='dulak-cluster' --create_scripts --compiler=gfortran43 campos-gpaw
    cp ~/RPMS/*/campos-gpaw-*.rpm /home/dulak-server/rpm/campos

    logout and login again!

Testing packages

Test dacapo installation (as normal user!).

If you use modules:

module load openmpi
module load campos-dacapo-pseudopotentials
module load python-numeric
module load campos-dacapo-python
module load ScientificPython
module load gnuplot-py
module load RasMol
module load campos-ase2
module load campos-dacapo
ulimit -s 65000 # dacapo needs a large stack

Test with (make sure that /scratch/$USER exists):

cp -r `rpm -ql campos-dacapo-python | grep "share/campos-dacapo-python$"` /tmp
cd /tmp/campos-dacapo-python/Tests
python 2>&1 | tee test.log

It can take up to 1 day. Please consider disabling these "long" tests in


Note all vtk related tests will fail.

Test gpaw installation (as normal user!):

If you use modules:

module load openmpi
module load campos-ase3
module load campos-gpaw-setups
module load campos-gpaw

Test with:

cp -r `rpm -ql campos-gpaw | grep "share/campos-gpaw/test$"` /tmp/test.gpaw.$$
cd /tmp/test.gpaw.*
python 2>&1 | tee test.log

It takes about 20 minutes.

On "Golden Client"

Login, as root, to the "Golden Client":

ssh n001

Enable nfs mount of the server home directory - follow 'Enable nfs mount on the "Golden Client"' from configuring NFS. After this do:

cd /home/dulak-server/rpm/campos

rpm -ivh campos-dacapo-2*

If getting:

package example_package.el5.i386 is already installed

remove these packages with:

rpm -e --nodeps example_package

to allow the installation to proceed.

Make sure that both python-numeric versions are installed:

rpm -q python-numeric

This command will show a list of packages that need to be installed to fulfill dacapo dependencies. All these packages should be already under /home/dulak-server/rpm. Remember to test the dacapo and gpaw installations on the "Golden Client" too.

If you are installing workstation only, your setup is ready for testing - go to benchmarking and maintenance.

If you are building a cluster go back to installing and configuring systemimager,