Platform LSF Administration Guide Version 6.2

Welcome
Administering Platform LSF
31
Data collection
◆ Data collection framework—new, lightweight method of collecting data from
multiple clusters.
◆ Month/level/date dimension—“Month” dimension is now included in all cubes.
◆ Pending time ranking—Workload cube includes “seconds”-level ranking for
pending time.
◆ UNIX exit code dimension—Workload cube collects data about the UNIX exit
code.
◆ Configuration data logging—collect data about LSF host group and user group
configuration for data logging.
◆ Redesigned job statistics cubes—Platform LSF Analytics will only collect data and
statistics concerning batch jobs. Within these jobs are interactive and parallel jobs.
Database
integration
◆ Daily reaggregation and data purge—Platform LSF Analytics has a daily table in the
database. Every day, data is reaggregated into this table, and obsolete data is purged
by default.
Out-of-box cubes
◆ Platform LSF Analytics has the following new license cubes:
❖ License usage by user group
❖ License utilization by feature
❖ License denial by feature
Platform LSF Windows desktop support
New operating system support
◆ Support for Windows 2000 with HP ProtectTools Authentication Services (WinSE)
Security
enhancements
◆ Blacklist and whitelist—you can use a blacklist or a whitelist to control a desktop
client's access to the desktop server to request work: to exclude only a few desktop
clients from requesting work, use a blacklist; to allow only a few desktop clients to
request work, use a whitelist.
◆ File caching control—you can specify whether a file can be cached on the desktop
client.
◆ Application authorization—you can configure LSF desktop support to run only
authorized applications.
◆ HTTP digest authentication—to ensure secure communication between the Web
Server and each desktop client, you can enable digest authentication.
Usability
◆ Tomcat and Apache are combined—only the default port (port 80) is used for both
file transfer and job control.
◆ New Logon and Idle desktop client modes—in Logon mode, jobs can run only
when no user is logged on to the desktop client; in Idle mode, jobs can run only
when the desktop client has been idle for a specified, configurable, period.
◆ Enhanced Screen saver desktop client mode—desktop client users can now use
their own screen saver instead of the default screen saver.