HPCI-SS
The HPCI-SS component is a variant of the Storage component that uses HPCI shared storage as the file storage location.
The properties you can set for the HPCI-SS component are as follows.
host
Set host to the host that runs the gfarm commands (gfcp, gfpcopy, etc.) used to transfer files to HPCI shared storage. The files themselves are stored on HPCI shared storage, not on the host itself.
However, only hosts that have the use gfarm option checked in the remotehost settings can be set as the host.
The HPCI-SS component always needs to transfer files to HPCI shared storage, so host is required. Unlike the Storage component, you cannot select localhost (a local path). If host is left unset, or set to localhost, running the project will fail with a validation error.
directory path
Similar to the Storage component, this is the path where files are actually stored. However, you must specify the path on HPCI shared storage, not a path on the host.
directory path is also required. Running the project with it left blank will fail with a validation error.
memo
You can enter free-form text here. Whatever you enter is included as-is, in the <memo> element,
in the GFarm extended-attribute metadata (wheel.workflow) attached to the file on HPCI shared
storage at transfer time. Use it to record the origin, purpose, or any other note about the
stored file.
Constraints
HPCI shared storage does not support overwriting copies to directories that already exist.
For this reason, when the HPCI-SS component receives a foo directory from a preceding component:
- On the first execution, a
foodirectory is created directly under the path specified in directory path, and the contents of the receivedfooare copied under thefoodirectory. - On subsequent executions, a directory named
WHEEL_TMP_XXXXXX(where XXXXXX is a random string) is created directly under directory path, and thefoodirectory is copied under it.