Cross-cluster user account mapping in IBM® Spectrum LSF Data Manager for a multicluster environment

Starting in Fix Pack 14, LSF Data Manager supports cross-cluster user account mapping for multiple clusters, allowing cross-cluster job submission and execution for a multicluster environment which has different user accounts assigned to different hosts. Using this feature, you can map user accounts in a local cluster to user accounts in one or more remote clusters. Cross-cluster mapping in LSF Data Manager is supported at the system level, and requires configuring your lsb.users configuration file on the remote and local clusters in your multicluster environment.

Before you begin

To use cross-cluster user account mapping in LSF Data Manager:

You must first configure LSF Data Manager for a multicluster environment.
For SCP (Secure Copy Protocol) of data in LSF Data Manager, the SSH public key must be shared between cross-cluster mapped user accounts. For example, if you have user1 from cluster1 with SSH key1, and user2 from cluster2 with SSH key2, data transfer jobs between these two users will be unsuccessful if they each have separate SSH public keys that are different. Therefore, ensure that both users share the same SSH public key users from either clusters can map SCP and SSH key information from each other.

Procedure

As an LSF administrator, map user accounts at the system level in the UserMap section of the lsb.users file to configure account mappings in a multicluster environment at the system level. Both the remote and local clusters must have corresponding mappings in their respective lsb.users files.
The required fields are LOCAL, REMOTE, and DIRECTION. These values map a user name on a local host to a different user name on a remote host so that jobs that execute on a remote host run using a mapped user name rather than the job submission user name.

For example, here are the lsb.users UserMap configuration for two clusters:
On cluster1:
```
Begin UserMap
LOCAL    REMOTE                             DIRECTION
user1    user2@lsfcluster2                  export
End UserMap
```
On cluster2:
```
Begin UserMap
LOCAL    REMOTE                             DIRECTION
user2    user1@lsfcluster1                  import
End UserMap
```
Run the bdata admin reconfig command from one LSF Data Manager hosts in the submission cluster, for the changes to take effect.

Results

Once you have lsb.users configured, you can run the bsub, bjobs, and bhist, as described in Cross-cluster user account mapping commands.