LSF Version 7.3 - Platform LSF Configuration Reference

Scope
Applicability Details
Operating system
•
UNIX hosts
•
Windows hosts
•
A mix of UNIX and Windows hosts within one or more clusters
Not required for
•
Multiple clusters with a uniform user name space
Dependencies
•
UNIX and Windows user accounts must be valid on all hosts in the cluster and must
have the correct permissions to successfully run jobs.
•
If users at your site have different user names on UNIX and Windows hosts within
a single cluster, you must configure between-host user account mapping at the
user level in .lsfhosts.
Limitations
•
You cannot configure this feature at both the system-level and the user-level; LSF
ignores system-level mapping if user-level mapping is also defined
in .lsfhosts.
•
If one or more clusters include both UNIX and Windows hosts, you must also
configure UNIX/Windows user account mapping.
•
If one or more clusters have different user accounts assigned to different hosts,
you must also configure between-host user account mapping for those clusters,
and then configure cross-cluster user account mapping at the system level only.
Configuration to enable cross-cluster user account mapping
•
LSF administrators can map user accounts at the system level in the UserMap section of
lsb.users. Both the remote and local clusters must have corresponding mappings in
their respective lsb.users files.
•
Users can map their local accounts at the user level in .lsfhosts. This file must reside
in the user’s home directory with owner read-write permissions for UNIX and owner read-
write-execute permissions for Windows. Save the .lsfhosts file without a file extension.
Both the remote and local hosts must have corresponding mappings in their
respective .lsfhosts files.
Restriction:
Define either system-level or user-level mapping, but not both.
LSF ignores system-level mapping if user-level mapping is also
defined in .lsfhosts.
Feature: Cross-cluster user account mapping
Platform LSF Configuration Reference 13