Platform LSF Reference Version 6.2

UserMap Section
Platform LSF Reference
470
UserMap Section
Optional. Used only in a MultiCluster environment.
Defines system-level account mapping for users and user groups.
To support the execution of batch jobs across non-uniform user name spaces between
clusters, LSF allows user account mapping. For a job submitted by one user account in
one cluster to run under a different user account in a remote cluster, both the local and
remote clusters must have the account mapping properly configured.
Structure
All three fields LOCAL, REMOTE and DIRECTION are required.
Example of a UserMap Section
On cluster1 Begin UserMap
LOCAL REMOTE DIRECTION
user1 user2@cluster2 export
user3 (user4@cluster2 user6@cluster2) export
End UserMap
On cluster2 Begin UserMap
LOCAL REMOTE DIRECTION
user2 user1@cluster1 import
(user6 user8) user3@cluster1 import
End UserMap
Cluster1 configures user1 to run jobs as user2 and user3 to run jobs as user4
or
user6.
Cluster2 configures user1 to run jobs as user2 and user3 to run jobs as user6
or
user8.
Only mappings configured in both clusters will work. The common account mappings
are for
user1 to run jobs as user2 and for user3 to run jobs as user6. Therefore,
these mappings will work, but the mappings of
user3 to user4 and user8 are only
half-done and so will not work.
LOCAL
A list of users or user groups in the local cluster.
Multiple user names and user group names must be separated by a space, and the entire
list enclosed in parentheses
().
REMOTE
A list of remote users or user groups in the form: user_name@cluster_name
user_group_name@cluster_name
Multiple user names and user group names must be separated by a space, and the entire
list enclosed in parentheses
().
DIRECTION
Configures the direction of account mapping: