RSM serves as a gateway for users wanting to submit jobs to a local or remote compute resource from applications such as Workbench.
The following are the main types of HPC resources to which RSM can be configured to submit jobs:
Commercial Cluster. Windows HPC, LSF, PBS Pro, SLURM, Altair Grid Engine (UGE), and custom clusters are supported. In this scenario, a third-party application takes care of job scheduling.
Ansys RSM Cluster (ARC). If you are not using a third-party job scheduler, you can use an Ansys RSM Cluster (ARC) as your scheduling system. This system is installed along with RSM. An ARC can be configured on the local machine, or on a remote one.
Third-Party Cloud. Provides access to Cloud-hosted compute services. Refer to RSM Custom Integration and contact Ansys customer support for assistance with integrating RSM with a Cloud.
Job submission is established through configurations that are defined using the RSM Configuration application. An RSM configuration for a cluster contains information about the cluster submit host, the system used for job scheduling, desired communication protocols, and the location of job directories. An RSM configuration for a Cloud portal identifies the portal URL. When defining an RSM configuration you also define RSM queues that will appear in client applications when users choose to submit jobs to RSM. Each RSM queue maps to a particular HPC queue. For more information about the components of an RSM configuration, refer to RSM Roles and Terminology, or the Glossary.
When configured successfully, RSM will:
Transfer job files from the client working directory to the HPC staging directory (if necessary)
Submit jobs to a cluster's job scheduler or a portal 's server application for scheduling and distribution
Monitor the job while it is running
Transfer requested output files back to the client working directory
Every RSM installation has one predefined configuration named
localhost. This configuration uses a basic Ansys RSM Cluster (ARC) to
submit jobs to the local machine. This enables users to run certain types of local jobs or
Mechanical background jobs right out of the box, without any special setup.
You can create as many RSM configurations as you need. Each RSM configuration that you define is stored in an .rsmcc file, and RSM queue definitions are stored in a single queues.rsmq file. These files are stored in a specified RSM configuration directory. Users who want to submit jobs to an HPC resource must have access to these files from their local machines. This can be accomplished by making the RSM configuration directory a shared directory, or having users copy the files to their local machines.
Important:
RSM should be configured by a system administrator.
If you will be defining RSM configurations that multiple people will use for remote job submission, and want to make them accessible to users through a shared directory, we recommend that you first change the location of the RSM configuration directory (the directory in which new configurations are saved). For more information see Setting the RSM Configuration Directory and Sharing and Accessing RSM Configurations.