Difference between revisions of "HPSS Frontends setup"
m (→Required Package) |
m |
||
| Line 44: | Line 44: | ||
Configuration files in /var/hpss/etc |
Configuration files in /var/hpss/etc |
||
| − | Copy ONLY needed files from |
+ | Copy ONLY needed files from core server or other frontend/client hosts. |
# ls /var/hpss/etc |
# ls /var/hpss/etc |
||
| Line 51: | Line 51: | ||
Adapt /var/hpss/etc/env.conf |
Adapt /var/hpss/etc/env.conf |
||
| − | # HPSS_API_HOSTNAME=<hostname of this |
+ | # HPSS_API_HOSTNAME=<hostname of this frontend/client host> |
| + | The contents of the file HPSS.conf can be used to set options for PFTP. Its a common place for settings that are grouped in stanzas. Setting network params for WAN connections is done here. |
||
| − | TODO: |
||
| − | Check if HPSS.conf is it needed? For my own tests it was not!! |
||
| − | Adapt HPSS.conf the client network options!!! |
||
| − | only to adapt if long distances betweek client and HPSS system |
||
| − | User Keytab |
+ | ==User Keytab== |
| − | A User keytab file must be copied into the |
+ | A User keytab file must be copied into the user directory and have minimal permissions |
# -rw------- 1 <user> <group> <user>.unix.keytab |
# -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: |
TODO: |
||
| − | If |
+ | If the frontend/client is outside the LSDF-KIT network, which ports to open to core and movers? |
Revision as of 01:03, 7 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. Its a common place for settings that are grouped in stanzas. Setting network params for WAN connections is done here.
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?
