HPSS
The Globus Connect Server HPSS Connector provides access to HPSS storage via Globus Connect Server.
This document describes the data types and API routes provided by this connector.
HPSS Connector Storage Gateway Policies
The HPSS Connector has the following policies to configure how it accesses HPSS.
HPSS Authentication
When a Globus user authenticates to a HPSS endpoint, the
HPSS Connector will first authenticate to HPSS using either
Kerberos or Unix authentication and the hpssftp user credential stored
on the local node. Then the hpssftp user session will change user ID
to the HPSS account that corresponds to the Globus user. In
this way, Globus users can authenticate to HPSS without
requiring a local HPSS key file for each user.
The authentication_mech and authenticator properties are used to
control how the HPSS Connector authenticates to HPSS.
authentication_mech sets the type of HPSS authentication to
use and accepts either krb5 or unix. authenticator specifies the
file containing an HPSS credential for the hpssftp user. The
authenticator property accepts a value of the form:
auth_keyfile|auth_keytab:<path_to_file>. This file must exist on all
nodes in the endpoint.
Store File Checksums in User Defined Attributes
The HPSS Connector can optionally store MD5 checksums in the
User-Defined Attributes (UDA) for use later with the sync-by-checksum
transfer mode. This allows the HPSS Connector to report the checksum
of an existing file without recalling the file from tape. This behavior
is controlled by the uda_checksum property which accepts either
true or false.