This document describes how to migrate workloads from IBM Tivoli Workload Scheduler (TWS) LoadLeveler (LoadLeveler) to IBM Platform Load Sharing Facility (LSF®).
This IBM Redpaper publication shows IBM Tivoli Workload Scheduler LoadLeveler users how to migrate their workloads to IBM Platform LSF. It explains the concepts and terminology of both workload management systems and maps LoadLeveler terms such as central manager, scheduler host, compute host, class, and requirements to their LSF equivalents (master host, queue, select, and so on). All LSF features mentioned in the paper are based on LSF V9.1.1.
The paper describes three main migration stages: setting up a simple LSF cluster to shadow the LoadLeveler cluster, migrating advanced features, and moving users and their jobs from LoadLeveler to LSF. It includes sample configurations that map LoadL_config, LoadL_admin, and lsb.queues settings to LSF files such as lsf.conf, lsf.shared, lsf.cluster.
| LSF version covered | V9.1.1 |
|---|---|
| Number of migration stages | Three |
| Default queue scheduling policy | First come, first served (FCFS) |
| LSF configuration file for cluster admins | lsf.cluster. |
It is a parallel job scheduling system that lets users run more jobs in less time by matching each job's processing needs and priority with available resources.
All LSF features mentioned in the paper are based on LSF V9.1.1.
First set up a simple LSF cluster to shadow the LoadLeveler cluster, then migrate advanced features, and finally move users and their jobs to LSF.
The LSF master host corresponds to the LoadLeveler central manager host, scheduler host, and master host.