News - HSI 6.0.0.p8

Announcing HSI 6.0.0.p8

(Jan 25, 2018)

NOTE: HSI/HTAR Support is no longer provided directly by Gleicher Enterprises

As of March 8 2017, HSI/HTAR support for HPSS sites is transitioning to the National Energy Research Scientific Computing Center (NERSC). See the Bugs/support page for more information

NOTE: HSI 5 (HSI 5.0.2) for HPSS 7.4.3 is in maintenance mode,

and will only receive bugfixes (no new features) going forward.  Sites are highly encouraged to upgrade to HPSS 7.5.1 and HSI/HTAR Version 6 as soon as possible.

HSI Version 6.0.0.p8 is now available for HPSS Release 7.5.1 sites.  

6.0.0.p8 contains bugfixes for problems that have been identified in earlier 6.0.0 versions, as well as the features descibed below, and we encourage all sites to upgrade to the new version.  

A list of the changes in this release, including those for 6.0.0.p5, p6 and p7, can be found here:

New Features in 6.0.0.p8

This release supports a new feature allowing HPSS administrators to control the maximum number of Virtual Volumes for which to issue concurrent background stages for HSI ‘get’ and ’stage’ commands.  

When this value is set to > 1 (the default), the HSI autoscheduler will attempt to issue background stage requests, in a round-robin fashion, for as many VVs as are allowed, and will not attempt to issue requests for a new VV until all stages for at least one of the active VVs has completed.

In addition, a new option is available to allow the admin to specify that all requested members of an aggregate be counted as a single stage when enforcing the “Max Background Stages”.  

Both of these new options are specified in the server-side HPSS.conf file, and take effect with each new HSI session.

The new HPSS.conf options, as contained in the 6.0.0.p8 misc/templates/HPSS.conf.template are:

     # BG Stage Max VVs.

     # This field is sent to the client during initial startup.

     # The  [case insensitive] setting is used to limit the maximum number of Virtual Volumes that 

     # are concurrently active for an individual background staging session.

     # The default if not specified is 1.

     # Note that the number of drives that will be used depends on the striping value for the 

     # storage class or the RAIT width.

     ;BG Stage Max VVs = 1

     # BG Stage Flags.

     # This field is sent to the client during initial startup.

     # The setting is a string of single-character flags for altering the default background

     # staging operation.

     # The default is to omit this setting.

     # Flag values are:

     #       A :  if set, background staging should attempt to stage all files in an aggregate that

     #            are asked for, overriding the Max Background Stages setting for the VV containing

     #            the aggregate. Effectively this counts all files in an aggregate as 1 stage entry.


     ; BG Stage Flags = A