HPSS Frontends setup: Difference between revisions
Line 57: | Line 57: | ||
== /etc/hosts == |
== /etc/hosts == |
||
Since the HPSS Server Nodes |
Since the HPSS Server Nodes are not in KIT DNS the /etc/hosts file on the Frontend host should be adapted like follows: |
||
# HPSS Production Hosts, Data Network |
# HPSS Production Hosts, Data Network |
Latest revision as of 10:43, 15 April 2015
Hosts that will run the hpss client/API must have several packages and files installed.
Required Package
Lots of packages can be found in the EPEL (Extra Packages for Enterprise Linux) repository. Better to install it.
# yum install epel-release
For HPSS also needed:
# yum install ksh # yum install libtirpc libtirpc-devel
HPSS Software download
https://hpss-collaboration.clearlake.ibm.com/adminwiki/doku.php
Path to rpms: HPSS Admin Wiki -> docs -> rpms -> <release>
Installation
Don't update hpss software, to keep old rpms. Always use rpm -i Option and not -U.
Create a hpss group
# groupadd -g 300 hpss
Install
# rpm -ivh hpss-lib-7.4.3.1-0.el6.x86_64 # rpm -ivh hpss-lib-devel-7.4.3.1-0.el6.x86_64 # rpm -ivh hpss-clnt-7.4.3.1-0.el6.x86_64 # rpm -ivh hpss-doc-7.4.3.1-0.el6.x86_64
Configuration
Remove old /opt/hpss link if exists
# rm /opt/hpss
Create new soft link
# ln -s /hpss_src/hpss-7.4.3.1-0.el6 /opt/hpss
Configuration files in /var/hpss/etc
Copy ONLY needed files from core server or other frontend/client hosts.
# ls /var/hpss/etc auth.conf authz.conf env.conf ep.conf hpss.unix.keytab site.conf
Adapt /var/hpss/etc/env.conf
# HPSS_API_HOSTNAME=<hostname of this frontend/client host>
The contents of the file HPSS.conf can be used to set options for PFTP and other clients (e.g. scrub). It's a common place for settings that are grouped in stanzas. Setting network params for WAN connections is done here.
/etc/hosts
Since the HPSS Server Nodes are not in KIT DNS the /etc/hosts file on the Frontend host should be adapted like follows:
# HPSS Production Hosts, Data Network 141.52.221.6 hpss.lsdf.kit.edu hpss hpsscr.lsdf.kit.edu hpsscr 141.52.221.7 hpsscr01.lsdf.kit.edu hpsscr01 hpsscr01-d 141.52.221.8 hpsscr02.lsdf.kit.edu hpsscr02 hpsscr02-d 141.52.221.11 hpssmvr01.lsdf.kit.edu hpssmvr01 hpssmvr01-d 141.52.221.12 hpssmvr02.lsdf.kit.edu hpssmvr02 hpssmvr02-d 141.52.221.13 hpssmvr03.lsdf.kit.edu hpssmvr03 hpssmvr03-d 10.97.202.14 hpssmvr04.lsdf.kit.edu hpssmvr04 hpssmvr04-d # HPSS Test system 141.52.221.50 hpsstcr03.lsdf.kit.edu hpsstcr03 hpsstcr03-d 141.52.221.51 hpsstmvr.lsdf.kit.edu hpsstmvr hpsstmvr-d
User Keytab
A User keytab file must be copied into the user directory and have minimal permissions
# -rw------- 1 <user> <group> <user>.unix.keytab
the following global variable can be used to direct clients to the keytab
# export HPSS_UNIX_KEYTAB_FILE=/home/jvw/HPSS/jvw.unix.keytab
TODO: If the frontend/client is outside the LSDF-KIT network, which ports to open to core and movers?