Resource manager translation allows end-users to continue to use existing job command scripts and familiar job management and resource query commands. This is accomplished by emulating external commands, routing the underlying queries to Moab, and then formatting the responses in a familiar manner. Using translation, job submission clients, job query clients, job control clients, and resource query clients can be emulated making switching from one resource manager to another transparent and preserving investment in legacy scripts, tools, and experience.
13.11.2 Translation Enablement Steps
The following steps are required to enable translation:
link translation tools to publicly accessible directory
configure tool behavior
13.11.2.1 Add Translation Tools
Included in the Moab <INSTALLDIR>/tools directory are a number of tools that can be linked to using the make.emulation.links script found in the buildutils directory. This script should be run as root and takes three arguments: the resource manager type, the source (tools) directory, and the destination (bin) directory. In the following example, Loadleveler translation tools are installed in the /usr/local/moab/bin directory.
NOTE: If run without any arguments, make.emulation.links reports usage information.
13.11.2.2 Configure Translation Tools
Located in the tools directory are tools-specific configuration files. For each resource manager that has installed translation tools, edit the corresponding configuration file in the tools directory. For example, if enabling Loadleveler translation, do the following: