Académique Documents
Professionnel Documents
Culture Documents
ANSYS, Inc.
Southpointe
275 Technology Drive
Canonsburg, PA 15317
ansysinfo@ansys.com
http://www.ansys.com
(T) 724-746-3304
(F) 724-514-9494
Disclaimer Notice
THIS ANSYS SOFTWARE PRODUCT AND PROGRAM DOCUMENTATION INCLUDE TRADE SECRETS AND ARE CONFIDENTIAL
AND PROPRIETARY PRODUCTS OF ANSYS, INC., ITS SUBSIDIARIES, OR LICENSORS. The software products and documentation are furnished by ANSYS, Inc., its subsidiaries, or affiliates under a software license agreement that contains provisions concerning non-disclosure, copying, length and nature of use, compliance with exporting laws, warranties,
disclaimers, limitations of liability, and remedies, and other provisions. The software products and documentation may
be used, disclosed, transferred, or copied only in accordance with the terms and conditions of that software license
agreement.
ANSYS, Inc. is certified to ISO 9001:2008.
Third-Party Software
See the legal information in the product help files for the complete Legal Notice for ANSYS proprietary software and
third-party software. If you are unable to access the Legal Notice, please contact ANSYS, Inc.
Published in the U.S.A.
Table of Contents
1. Overview ................................................................................................................................................. 1
1.1. RSM Roles and Terminology .............................................................................................................. 1
1.2. Typical RSM Workflows ...................................................................................................................... 2
1.3. File Handling .................................................................................................................................... 4
2. Installation and Configuration ............................................................................................................... 7
2.1. Installation ....................................................................................................................................... 7
2.1.1. Prerequisites for Installing RSM ................................................................................................. 7
2.1.2. Installing Standalone RSM Services on Linux ............................................................................. 7
2.1.3. Installing Standalone RSM Services on Windows ....................................................................... 7
2.1.4. Uninstalling RSM Services on Windows ..................................................................................... 8
2.2. Configuration ................................................................................................................................... 8
2.2.1. Configuring RSM on Windows .................................................................................................. 8
2.2.1.1. Starting RSM Services at Boot Time .................................................................................. 8
2.2.1.2. Configuring RSM for Mapped Drives ................................................................................ 8
2.2.2. Configuring RSM on Linux ........................................................................................................ 8
2.2.2.1. UNIX/Linux Path Configuration Requirements .................................................................. 9
2.2.2.2. Configuring RSM to Use a Remote Computing Mode ........................................................ 9
2.2.2.2.1. Configuring a Linux Machine to Use Native Mode .................................................. 10
2.2.2.3. Using RSM Startup Scripts .............................................................................................. 10
2.2.2.4. Starting RSM Manager and Compute Server Services Manually ....................................... 11
2.2.2.4.1. Starting the RSM Manager Manually ...................................................................... 11
2.2.2.4.2. Starting the Compute Server Manually .................................................................. 11
2.2.2.4.3. Starting XmlRpcServer Manually (Required for EKM Servers Only) .......................... 11
2.2.2.5. Starting RSM Services at Boot Time ................................................................................ 11
2.2.2.6. Removing the RSM Automatic Startup Capability ........................................................... 12
2.2.2.7. Additional UNIX/Linux Considerations ........................................................................... 13
2.2.2.7.1. Explicit Dynamics Systems .................................................................................... 13
2.2.2.8. RSH and SSH Job Limitations ......................................................................................... 13
2.2.3. Configuring a Multi-User RSM Manager or Compute Server ..................................................... 13
2.2.4. Configuring RSM Services for a Remote Computing Environment ............................................ 14
2.2.4.1. Adding a Remote Connection to an RSM Manager .......................................................... 14
2.2.4.2. Adding a Remote Connection to a Compute Server ........................................................ 14
2.2.4.3. Configuring Computers with Multiple Network Interface Cards (NIC) .............................. 15
3. User Interface ........................................................................................................................................ 17
3.1. Main Window ................................................................................................................................. 17
3.2. Menu Bar ........................................................................................................................................ 18
3.3. Tree View ........................................................................................................................................ 19
3.4. List View ......................................................................................................................................... 20
3.5. Progress Pane ................................................................................................................................. 21
3.6. Options Dialog Box ......................................................................................................................... 21
3.7. Desktop Alert ................................................................................................................................. 22
3.8. Accounts Dialog Box ....................................................................................................................... 22
3.9. Windows RSM System Tray Icon and Context Menu .......................................................................... 23
4. User Accounts and Passwords ............................................................................................................... 25
4.1. Caching an Account Password ......................................................................................................... 25
4.2. Manually Running the Password Application ................................................................................... 25
4.3. Adding Alternate Accounts ............................................................................................................. 26
4.4. Configuring UNIX/Linux Accounts When Using RSH/SSH .................................................................. 26
5. Administration ...................................................................................................................................... 29
5.1. Creating a Queue ............................................................................................................................ 29
ANSYS Release 13.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.
iii
iv
ANSYS Release 13.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.
Chapter 1: Overview
The Remote Solve Manager (RSM) is a job queuing system that distributes tasks that require computing resources. RSM enables tasks to be run in background mode on the local machine, sent to a remote machine
for processing, or tasks can be broken into a series of jobs for parallel processing across a variety of computers.
Computers with RSM installed are configured to manage jobs using three primary services: The RSM Client
service, the RSM Manager service, and the Compute Server service. You use the RSM Client interface to
manage jobs.
RSM Clients submit jobs to a queue, and the RSM Manager dispatches these jobs to idle Compute Servers
that run submitted jobs. These services and their capabilities are explained in RSM Roles and Terminology (p. 1)
The following topics are discussed in this overview:
1.1. RSM Roles and Terminology
1.2.Typical RSM Workflows
1.3. File Handling
ANSYS Release 13.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.
Chapter 1: Overview
RSM Manager
The RSM Manager is the central RSM service that dispatches jobs to computing resources. It contains a
configuration of queues (lists of Compute Servers available to run jobs).
RSM Clients submit jobs to one or more queues configured for the RSM Manager, and their jobs are
dispatched to Compute Servers as resources become available.
The RSM administrator decides if users should use the RSM Manager on their local machine or a central
RSM Manager, depending on the number of users and compute resources.
RSM Client
The RSM Client is a computer that runs both RSM and a client application such as ANSYS Workbench.
RSM enables this computer to off-load jobs to a selected queue.
Compute Proxy
Proxy settings are used by job scripts to integrate with third-party job schedulers (for example, LSF, PBS,
Microsoft HPC) and UNIX/Linux machines (when native RSM service is not available).
Code Template
A code template is an XML file containing code files (for example, C#, VB, JScript), references, and support
files required by a job.
The RSM Client submits jobs using RSM (running locally) directly to itself so that the job runs locally
in background mode. Here, the RSM Client, the RSM Manager, and the Compute Server are all on the
local machine. This capability is available automatically when you install ANSYS Workbench.
2.
The RSM Client submits jobs to the RSM Manager running locally on the same machine. You can assign
a remote Compute Server to run the job or split the job between multiple Compute Servers, optionally
including your local machine (as depicted in the second workflow below). A remote Compute Server
requires RSM and the client application to be installed (the client application is typically installed with
ANSYS Workbench, which also includes RSM).
ANSYS Release 13.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.
3.
An RSM Client machine submits jobs to an RSM Manager running on a remote machine (refer to Adding
a Remote Connection to an RSM Manager (p. 14)). The remote machine also acts as the Compute Server.
This configuration is available automatically when both machines have ANSYS Workbench installed.
4.
An RSM Client machine submits jobs to an RSM Manager running on a remote machine. The RSM
Manager then assigns the job to a remote Compute Server(s). The RSM Client and the Compute Servers
must have ANSYS Workbench installed. You can install ANSYS Workbench on the RSM Manager, or
choose to install only standalone RSM software, as described in Installation (p. 7).
ANSYS Release 13.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.
Chapter 1: Overview
ANSYS Release 13.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.
ANSYS Release 13.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.
ANSYS Release 13.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.
2.1. Installation
RSM is automatically installed with ANSYS Workbench products. You can also install RSM by itself if desired.
For example, you may want to install RSM by itself on a computer that acts as a dedicated RSM Manager;
an RSM Manager requires only an RSM installation for connectivity with remote RSM Clients and Compute
Servers. RSM Clients and Compute Servers require ANSYS Workbench, the ANSYS applications you want to
run, and RSM. Administrator privileges are not required to install or uninstall RSM on RSM Client machines.
The following RSM installation topics are discussed in this section:
2.1.1. Prerequisites for Installing RSM
2.1.2. Installing Standalone RSM Services on Linux
2.1.3. Installing Standalone RSM Services on Windows
2.1.4. Uninstalling RSM Services on Windows
2.
Ensure that Ans.Rsm.* processes are not running in the Windows Task Manager.
ANSYS Release 13.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.
4.
Note
Windows Vista and Windows 7 users may need to select the Run as Administrator option.
2.2. Configuration
The following RSM configuration topics are discussed in this section:
2.2.1. Configuring RSM on Windows
2.2.2. Configuring RSM on Linux
2.2.3. Configuring a Multi-User RSM Manager or Compute Server
2.2.4. Configuring RSM Services for a Remote Computing Environment
For more information on configuring RSM Clients and Compute Servers using a network installation, please
refer to Network Installation and Product Configuration.
ANSYS Release 13.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.
Note
~ (tilde) representation of the home directory is not supported for use in RSM paths (for example, the working directory in Compute Server properties).
Different shells use different initialization files than the account's home directory and may
have a different syntax than shown above. Refer to the UNIX/Linux man page for the specific
shell or consult the machine administrator.
SSH communication
Protocol Type
Installation Requirements
Platform Support
ANSYS recommends that you use native communication where possible, and use SSH where platform support
or IT policy requires it.
ANSYS Release 13.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.
Run the ./rsmmanager and ./rsmserver scripts to manually start the RSM Manager and Compute
Server services. Refer to Starting RSM Manager and Compute Server Services Manually (p. 11) for more
information.
2.
Configure RSM to start the RSM Manager and Compute Server services at boot, as described in Starting
RSM Services at Boot Time (p. 11)
3.
On the RSM Client machine, configure the Computer Server Properties as shown below, substituting
a valid hostname and working directory (refer to Adding a Compute Server (p. 30) for more information
on configuring Compute Server properties):
Note
These shell scripts are dependent on their relative location in the Workbench installation so they
cannot be moved. This is not the case with the daemon scripts (rsmmanager and rsmserver).
10
ANSYS Release 13.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.
XmlRpcServer - Starts the XmlRpcServer service (required for EKM servers only).
ANSYS Release 13.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.
11
Note
The procedure described in this section starts a service as root. It is not essential that the RSM
services run as root user.
Instructions
1.
2.
Note
Non-root user cannot save changes to this file.
3.
Linux: SUSE
1.
2.
Note
Non-root user cannot save changes to this file.
3.
After you have completed the procedure to start a service automatically at boot time, reboot the system to
verify that the automatic boot procedure is working correctly. After the system has rebooted, check to see
that services are running by typing the appropriate ps command and looking for Ans.Rsm in the resulting
display; for example:
ps aux | grep Ans.Rsm
12
ANSYS Release 13.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.
Note
Before customizing job scripts, consult ANSYS Technical Support or your ANSYS Software
Distributor to check if new job scripts have been made available after release.
The RSH protocol is not officially supported at 13.0 and will be completely removed from
future releases. Windows Server 2008, Windows Vista, and Windows 7 do not include the
RSH client. It may be possible to use a third-party RSH client on these Windows versions with
some customization; however, PuTTY SSH is the recommended alternative.
All RSM users should have write access to the RSM working directory. The default working directory
may not function properly if write permissions are not enabled for all applicable users.
All RSM users should cache their account password (refer to Caching an Account Password (p. 25)). If all
users do not cache their password, only the user that started RSM on the machine can submit jobs.
When installing RSM to a multi-user Linux machine, ANSYS strongly recommends that you set up RSM
as a daemon (refer to Starting RSM Manager and Compute Server Services Manually (p. 11)). Running RSM
ANSYS Release 13.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.
13
If you are running ANSYS Workbench on a multi-user RSM machine, My Computer, Background (see
Using Solve Process Settings in the Mechanical User's Guide) will likely not function as expected with
Rigid Dynamics or Explicit Dynamics due to write permissions for RSM working directories. As a workaround for this issue, follow these guidelines:
Ensure that RSM Manager and Compute Server (ScriptHost) processes always run under the same
user account. This will ensure consistent behavior.
Do not use the built-in My Computer or My Computer Background solve process settings.
Add a Remote Solve Process Setting that specifies that the Solution Manager name is the machine
name, rather than localhost. Refer to Using Solve Process Settings in the Mechanical User's Guide
for more information.
To run more than one job simultaneously, adjust the Max Running Jobs property in the Compute
Server Properties dialog box.
Note
When communicating with a remote computer, whether RSM Client to RSM Manager or RSM
Manager to Compute Server, RSM services must be installed on those computers.
Launch RSM.
2.
In the RSM main window select Tools > Options. The Options dialog box appears.
3.
In the Name field, enter the name of a remote machine with the RSM Manager service installed.
4.
Select the Add button and then OK. The RSM Manager and all of its queues and Compute Servers
appear in the Tree View.
5.
Passwords are cached on the RSM Manager machine, so you must set the password again. Refer to
Caching an Account Password (p. 25) for this procedure.
14
If the Compute Server is running Windows, only the machine name is required in the Friendly Name
field in the Compute Server Properties dialog box.
ANSYS Release 13.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.
If the Compute Server involves integration with a Linux/UNIX machine or another job scheduler, refer
to Appendix A (p. 39) or Appendix B (p. 43) for integration details.
Ensure that you have administrative privileges to the working directory of the new Compute Server.
Always test the configuration of a connection to a new remote Compute Server after it has been created,
as described in Testing a Compute Server (p. 32).
2.
Open both files in a text editor, and add machineName=ip_address to the TCP channel configuration as shown below, substituting a valid IP address for "ip_address". Do not change any other
information in the string.
...
<channels>
<channel ref="tcp" port="9012" secure="false" machineName="ip_address">
<serverProviders>
<formatter ref="binary" typeFilterLevel="Full"/>
</serverProviders>
</channel>
</channels>
...
Note
To determine the correct IP address to use, use the ping utility at the command prompt
from a separate computer using the multi-NIC computers DNS name. For example:
C:\>ping multiNICmachine
Pinging multiNICmachine.mycompany.com [10.2.10.32] with 32 bytes of data:
Reply from 10.2.10.32: bytes=32 time=56ms TTL=61
In this example, the IP address 10.2.10.32 represents the network that RSM Clients have
identified.
3.
4.
Restart both the Ansys JobManager Service V13 and Ansys ScriptHost Service V13 services in the
Windows Services dialog box. To launch the Windows Services dialog box, Windows XP users can
open this dialog box by selecting Control Panel > Administrative Tools > Services. Windows 7 and
Vista users can open the dialog box by selecting Control Panel > System and Security > Administrative Tools > Services. To restart these services, right-click on the desired service, then select Restart.
ANSYS Release 13.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.
15
2.
3.
4.
16
ANSYS Release 13.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.
Windows users select Start > All Programs > ANSYS 13.0 > Utilities > Remote Solve Manager
The RSM main window interface elements are described in the table that follows.
Interface Element
Description
Menu Bar
Provides access to the following menus: File, Options, View, Tools, and Help.
ANSYS Release 13.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.
17
Description
Toolbar
Show displays a list that filters jobs. Filter options include: All Jobs, Completed,
Running, Queued, and Failed.
Delete deletes a currently selected job or jobs. The function is the same as using
the Remove option of the List View context menu or the Delete key.
All Owner Jobs displays or hides jobs that belong to owners other than yourself.
The function is the same as using View > All Owner Jobs in the Menu Bar.
Progress Pane displays or hides the Progress Pane. The function is the same as
using View > Progress Pane in the Menu Bar.
Tree View
Displays configured queues and servers for one or more RSM Managers.
List View
Progress Pane
Status Bar
The Job Count Pane displays the number of jobs displayed in the List View.
Selections
Function
File
Close
Hides the main window. RSM continues to run in the tray. Right
click the system tray icon and select the Exit option in the
Context Menu to exit RSM.
Options
Always On Top
If checked, RSM will not appear in the task bar when minimized;
it only appears as a tray icon (Windows only).
Progress Pane
Refresh Now
Update Speed
View
18
ANSYS Release 13.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.
3.3.Tree View
Menu
Selections
Function
Tools
Desktop Alert
Remove
Submit a Job
Options
Help
When a Queues node is selected, only the Add... option is available in the context menu.
When a queue is selected, the Properties... and Delete... options are available in the context menu.
ANSYS Release 13.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.
19
When a Compute Server is selected under a Queues node or under a Compute Servers node, the Properties...
and Test Server... options are available. The Delete... option (not shown) becomes available if a Compute
Server that is not assigned to any queue is selected under a Compute Servers node.
When a Compute Servers node is selected, only the Add... option is available.
For more information on using the Tree View context menu options, see Administration (p. 29).
ANSYS Release 13.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.
Note
If a job is running you cannot remove it. Use the Cancel option in the List View context menu,
then wait for the job to complete. Sending a cancel command to a job allows it to cleanup processes spawned by the job. There may also be a job stopping option in the client application that
submitted the job (for example, ANSYS Workbench Mechanical Stop Solution command).
The List View context menu provides the following options:
Inquire
Inquire about a running job. This action depends on the type of job being run. Generally, the Inquire
command will run some additional job script code to perform some action on a running job. It can also
bring back intermediate output and progress files.
Cancel
Cancel a running job. The job script implements cancel code to cleanup spawned process and perform
any necessary cleanup.
Remove
Deletes the selected job or jobs.
Set Priority
When jobs are submitted they have a default priority of Normal. To change the priority of a Queued
job, right-click on the job name, choose Set Priority, and change the priority. The higher priority jobs
in a queue run first. Changing the priority of a job that is in any state except Queued has no effect. Only
RSM administrators can change a job priority to the highest level.
Bottom Option
Allows job add-ins to provide specific functionality for that type of job (if available). A job add-in may
display specific information about the running job, such as an output file (Inquire may be required to
update the file). The add-in functionality allows for more detailed information about a job without running
the RSM Client software that submitted the job. The add-in can also be used on a different computer
than where the job was originally submitted.
Note
When making a support call concerning RSM functionality, the complete contents of the Progress
Pane should be sent.
ANSYS Release 13.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.
21
Solve Managers - Lists available RSM Manager machines. You can Add or Delete RSM Managers, or
Change machine names in the list.
Desktop Alert Settings - Contains check boxes to configure the following desktop alerts:
22
ANSYS Release 13.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.
Menu Option
Description
Options
Help
About
Desktop Alert
Exit
ANSYS Release 13.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.
23
24
ANSYS Release 13.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.
Note
It is not necessary to cache your password with the RSM Manager if you are using RSM only for
local background jobs. Additional configuration may be required to use remote compute resources.
To cache an account password:
1.
In the Tree View, right-click on the RSM Manager and select Set Password. In a Windows environment,
this opens a command window. In a Linux environment, the password application runs in the terminal
where the RSM user interface was started. If the RSM user interface was not started in a terminal, you
can run the password application manually (see Manually Running the Password Application (p. 25)).
2.
Press Enter at the username prompt to set the password for the currently logged-in user.
3.
4.
ANSYS Release 13.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.
25
26
ANSYS Release 13.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.
Note
The RSH protocol is not officially supported at 13.0 and will be completely removed from future
releases. Windows Server 2008, Windows Vista, and Windows 7 do not include the RSH client. It
may be possible to use a third-party RSH client on these Windows versions with some customization, however, PuTTY SSH is the recommended alternate.
ANSYS Release 13.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.
27
28
ANSYS Release 13.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.
Chapter 5: Administration
Users with RSM administrator privileges can perform a variety of additional tasks. For instance, RSM administrators can create and modify RSM Managers and Compute Servers, manage queues, set jobs to highest
priority, and delete jobs of any user.
RSM administrators must fulfill one of the following requirements:
RSM administrator is a Windows administrator on the RSM Manager machine (they are in the local or
domain administrators group).
RSM administrator has been made a member of the RSM Admins group on the RSM Manager machine.
In this case, the RSM services (ANSYS JobManager Service V13 and ANSYS ScriptHost Service V13)
may need to be restarted for administrator privileges to take effect.
In the Tree View, right-click on the Queues node for a desired RSM Manager.
2.
3.
Queue Properties:
Name
This field should contain a descriptive name for the queue. Examples of queue names include
Local Queue, Linux Servers, or HPC Cluster. If the Compute Server(s) in the queue has a
Start/End Time specified you may want to use a name that indicates this to users (e.g., "Night Time
Only").
ANSYS Release 13.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.
29
Chapter 5: Administration
Enabled
If True, the RSM Manager dispatches queued jobs to available Compute Servers. If False, jobs remain
in a "Queued" state until the queue is enabled.
Priority
This value can be Low, Below Normal, Normal, Above Normal, or High. When determining the
next job to run, the RSM Manager pulls jobs from the highest priority queue first. Priority settings
are commonly used to create a separate, higher priority queue for smaller jobs, so that they are
processed before running large jobs that tie up the computing resource for a long period of time.
Assigned Servers
Check the Compute Servers that are used in this queue. A queue can contain more than one
Compute Server. A Compute Server can also be a member of more than one queue.
2.
3.
Modify Solve Manager Properties described below, and then select OK.
In the Tree View, right-click on the Compute Servers node for the desired Compute Server.
2.
30
ANSYS Release 13.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.
3.
Configure Compute Server Properties described below, then select OK. Optionally, you can test a
Compute Server after it has been created.
Compute Server Properties:
1. General
Friendly Name
Any descriptive name for the Compute Server. This is intended as an easy-to-remember
alternative to the Machine Name. Examples of friendly names include Bobs Computer,
or My Computer to Linux Proxy.
The Friendly Name is initialized to Server (date time) to guarantee its uniqueness.
Machine Name
The name of a computer that has RSM and the client application installed. Use "localhost"
for the local machine or the network machine name to identify a remote machine.
Enabled
If True, this Compute Server can accept jobs.
Working Directory
The directory on the Compute Server where the job is run. Job scripts, input files, and
output files are located in this directory. If blank, the system temporary directory is used,
which is defined by the TMP environment variable. RSM users must have write access and
full permissions to this directory.
Logging Enabled
If True, a log file is created in the Working Directory on the RSM Manager machine. The
file name has the form RSM_machine.log.
Max Running Jobs
The maximum number of simultaneous jobs this Compute Server is allowed to run. This is
required to prevent collisions, which can occur because RSM cannot detect the number of
cores on a machine. In previous versions, to run multiple jobs on one Compute Server it
was necessary to create duplicate servers differing only in name and add them to the same
queue. This is no longer necessary. This is especially useful when the job is simply forwarding
the work to a proxy job scheduler (for example, LSF, PBS).
ANSYS Release 13.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.
31
Chapter 5: Administration
Important
Max Running Jobs applies to only the current instance of RSM. If more than
one version (e.g., 11.0, 12.1, etc.) of RSM is used to submit jobs, collisions between
jobs can occur. RSM cannot detect jobs being assigned to a Compute Server by
differing versions of RSM.
Start Time
Time (in 24-hour HH:MM:SS format) at which the Compute Server can accept jobs. Use
00:00:00 for both Start Time and End Time for 24 hour availability. Start Time is very
useful if a Compute Server or application licenses are only available at certain times of the
day.
End Time
Time (in 24-hour HH:MM:SS format) at which time the Compute Server stops accepting
jobs. Jobs already running at the end time continue to run. Use 00:00:00 for both Start
Time and End Time for 24 hour availability.
2. Compute Proxy
Keyword
Keywords invoke customized job scripts. For example, the standard code template for an
ANSYS Solver job is AnsysCode.xml. If the keyword RSH is entered, the code template
AnsysCode_RSH.xml is used, which contains a different set of code files designed to
communicate with another computer using the RSH/RCP protocol. The remaining proxy
settings are used exclusively by the custom job script.
Machine Name
Use this proxy setting to specify a non-Windows compute proxy machine. This value is accessed with the Task.ProxyMachine property in the job script. Custom job scripts can
use this setting for any purpose.
Account Name
Use this proxy setting to specify an account name on a non-Windows compute proxy machine. This value is accessed with the Task.ProxyAccount property in the job script.
Custom job scripts can use this setting for any purpose. A blank entry is allowed.
Working Directory
Use this proxy setting to specify a working directory on the non-Windows compute proxy
machine. This value is accessed with the Task.ProxyPath property in the job script.
Custom job scripts can use this setting for any purpose. A blank entry is allowed.
Custom 1
Use this reserved field to send parameters to a customized job script. The value is accessed
with the Task.Custom1 property.
Custom 2
Use this reserved field to send parameters to a customized job script. The value is accessed
with the Task.Custom2 property.
ANSYS Release 13.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.
Note
If you do not have full permissions to the Compute Server working directory, Compute Server
tests will fail.
ANSYS Release 13.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.
33
34
ANSYS Release 13.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.
Visual Studio projects are supplied in the scripts folder to aid in editing.
The job script files are delivered in the C# language. Theoretically, it is possible to use other .NET-supported
languages (for example, Visual Basic, Jscript), but this has not been officially tested. C++ may also be supported
in future release.
Keywords
Keywords are used to invoke specialized scripts to integrate with non-native operating systems (for example,
UNIX, Linux) and third-party job schedulers (for example, LSF, Microsoft HPC). The keyword is appended to
the base job code template name. For example, if the code template is named ServerTestCode.xml
and the keyword is LSF, RSM will first look for ServerTestCode_LSF.xml. Keywords are the best way
to invoke custom scripts without affecting the existing jobs.
Job Templates
Job templates define the code template, inputs, and outputs of a job. Job template files are located in
[RSMInstallDirectory]\Config\xml on the RSM Manager machine.
The job template for a server test job is shown below:
<?xml version="1.0" ?>
<JobTemplate>
<script>ServerTestCode.xml</script>
<debug>TRUE</debug>
<cleanup>TRUE</cleanup>
<inputs>
<file type="ascii">*.in</file>
</inputs>
<outputs>
<file type="ascii">*.out</file>
</outputs>
</JobTemplate>
ANSYS Release 13.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.
35
Code Templates
Code templates contain sections for the actual code files, referenced assemblies (.dlls), and support files
(such as localized strings). These files are transferred to the Compute Server and processed by the
ScriptHostService on that computer. Code templates are located in [RSMInstallDirectory]\Config\xml on the RSM Manager machine.
A code template for a server test job is shown below:
<?xml version="1.0" ?>
<codeDefinition>
<codeFiles>
<codeFile>ServerTest.cs</codeFile>
</codeFiles>
<references/>
<supportFiles/>
</codeDefinition>
36
ANSYS Release 13.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.
Submitting Solutions for Local, Background, and Remote Solve Manager (RSM) Processes in the Workbench
User's Guide
RSM specific tutorials featuring step-by-step instructions for specific configuration scenarios on the
Download Center at https://www1.ansys.com/customer/
Mechanical APDL
CFX
FLUENT
Polyflow
Some applications may not always work with remote Compute Servers or RSM Managers.
When a client application is restricted to the RSM Client machine, RSM enables the client application
to run in the background.
When a client application can send jobs to remote Compute Servers, the job may be run completely
on one Compute Server, or the job may be broken into pieces so that each piece can run in parallel on
multiple Compute Servers (possibly including the RSM Client machine). In the case where a job is being
run in parallel on multiple machines, you need to ensure that the software that controls the parallel
processing is supported on all of the Compute Servers.
ANSYS Release 13.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.
37
38
ANSYS Release 13.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.
2.
3.
a.
Run PuTTYGen (puttygen.exe). The Putty Key Generator dialog box appears.
b.
Select Generate.
c.
d.
Change the key comment to include your machine name and Windows username.
e.
Save the private key file without passphrase, for example, <drive>:\Program
Files\Putty\id_rsa.ppk. Using a pass phrase results in jobs being hung at a prompt to
enter the pass phrase. Be sure to secure the private key file using some other means. For example,
if the key is only being used by you, save it to the My Documents folder where only you and administrators have access to the file. If multiple users share the same key, allow the owner full
control, then create a group and allow only users in that group to read this file.
f.
Move the public portion of the key to the UNIX machine. This requires you to edit the
~/.ssh/authorized_keys file on the UNIX machine. Edit the file in a telnet session on the
Windows machine. Copy all the text from the box under "Public key for pasting" and paste it
into ~/.ssh/authorized_keys. All of this text should be one line. If the authorized_keys
file does not exist, create one. Alternately, paste it into a text file and move that file to the UNIX
machine for editing.
g.
Modify permissions to allow read and execute by running chmod 600 .ssh/authorize_keys.
Open the Windows System Properties dialog box. Windows XP users select Control Panel >
System. Windows Vista and Windows 7 users select Control Panel > System and Security >
System > Advanced.
b.
In the Advanced tab, select Environment Variables. The Environment Variables dialog box
appears.
c.
In the Environment Variables dialog box, locate the Path variable in the System variables pane.
ANSYS Release 13.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.
39
4.
d.
Select the Path variable then click the Edit button. The Edit System Variable dialog box appears.
e.
Add the PuTTY install directory to the Variable value field (for example, C:\Program Files\putty),
then click OK.
f.
In the Environment Variables dialog box, click the New button. The New System Variable dialog
box appears.
g.
In the New System Variable dialog box, create a new environment variable named KEYPATH
with a value containing the full path to the private key file (for example, <drive>:\Program
Files\Putty\id_rsa.ppk). Use a user variable if the key file is used only by you. Use a system
variable if other users are sharing the key file. For example, if a Windows XP user has a key file in
My Documents, the variable value should be %USERPROFILE%\My Documents\id_rsa.ppk
(this expands to <drive>:\Documents and Settings\<user>\My Documents\id_rsa.ppk).
h.
Click OK.
i.
Test the configuration by running the following from the command prompt (quotes around %KEYPATH%
are required):
plink -i %KEYPATH% unixlogin@unixmachinename pwd
5.
40
a.
b.
Add a new Compute Server in RSM using the Keyword "PSSH" as shown below. Refer to Adding a
Compute Server (p. 30) for more information.
ANSYS Release 13.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.
6.
On the Linux Compute Server machine, ensure that the ANSYS Product environment variable
AWP_ROOT130 is set to the location of your ANSYS product installation. This is done by adding the
environment variable definition to your .cshrc resource file.
7.
ANSYS Release 13.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.
41
42
ANSYS Release 13.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.
Note
The RSH protocol is not officially supported at 13.0 and will be completely removed from future
releases. Windows Server 2008, Windows Vista, and Windows 7 do not include the RSH client. It
may be possible to use a third-party RSH client on these Windows versions with some customization; however, PuTTY SSH is the recommended alternate.
RSH Configuration
In order to send jobs to a remote UNIX/Linux machine using RSH, RSH must be configured to allow access
from a specific user and a specific machine. Edit the .rhosts file in the home directory of the UNIX/Linux
account where the job runs to allow access. The entry is of the form:
windows_machine_name windows_username
or
windows_machine_IP windows_username
For example, if the Windows domain account is COMPANY\johnd and the Windows Compute Server is
named jdoexp06, the .rhosts entry would be:
jdoexp06 johnd
ANSYS Release 13.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.
43
Along with the Test Server feature, use the troubleshooting commands below to verify the RSH configuration.
These commands are executed at the Windows command prompt on the RSM Manager that communicates
directly with the UNIX/Linux Compute Server.
1.
If Windows and UNIX/Linux account names match, the following command lists the home directory
on the remote machine:
C:\>rsh unixmachine ls -l
2.
If the Windows and UNIX/Linux account names are different, the following command lists the home
directory of unixaccount on the remote machine:
C:\>rsh unixmachine -l unixaccount ls -l
44
ANSYS Release 13.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.
The Working Directory and Proxy Working Directory values are the same physical location. The network
share representation is the staging area for job inputs and outputs and is accessed from the LSF execution
host. This directory and share must exist on all nodes. In this example, there must be a D:\RSMTemp
and share \\nodename\RSMTemp on all nodes.
The RSM job script submits the job to LSF with the following bsub command. This code is located in the
file RSMInstallDir\RSM\Config\scripts\LSFUtilties.cs.
bsub q queue n numCPUs o stdout.out e stderr.out cscript.exe //nologo LSF_Job.js control.txt
The number of CPUs is dependent on the specific job. For example, for the ANSYS Solver, the number of
CPUs is parsed from the command line coming from ANSYS Workbench. The LSF job is a JScript named
LSF_Job.js located in RSMInstallDir\RSM\Config\scripts. This script does the following:
1.
2.
3.
4.
5.
6.
Cleans up.
ANSYS Release 13.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.
45
Note
For a server test (RSMInstallDir\RSM\Config\scripts\TestServer_LSF.cs), the
queue is hard-coded to normal and the number of CPUs is set to 2. Edit this file if these default
settings are not appropriate.
To complete the configuration, create a new queue and add the Compute Server to it. The RSM queue
name must match the LSF queue name exactly. Jobs can now be submitted to this queue and then forwarded to the LSF queue for scheduling.
You can set the Max Running Jobs property to the value appropriate to your cluster. Note that the RSM
job could be in a Running state, but LSF may not yet be able to execute the job due to limited resources.
Refer to the Progress Pane to determine LSF job ID and state.
46
ANSYS Release 13.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.
2.
3.
4.
5.
6.
Cleans up.
Now create a new queue and add this Compute Server to it. Jobs can now be submitted to this queue and
then forwarded to the Microsoft HPC for scheduling.
The number of CPUs/nodes allocated by Microsoft HPC is controlled by the job script implementation. For
example, the Mechanical application contains a Max number of utilized processors setting that is passed
along on the solver command line. The command line is parsed in the job script and this information is
passed on to Microsoft HPC. The number of CPU requests is reported in the Progress Pane.
ANSYS Release 13.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.
47
Passwords
RSM no longer requires users to manually cache their Windows password with Microsoft HPC. Each RSM job
runs the hpcutils.exe tool prior to submitting the job to the cluster. This tool programmatically does
the equivalent of cluscfg setcreds.
Mixed Domains
You can use RSM when the client computer and the cluster are different domains. The assumption is that
the client computer and user account are on the corporate domain and the cluster is its own domain. In
this case, the cluster domain must be configured to have a one-way trust with the corporate domain. That
is, the cluster domain trusts the corporate domain but not vice-versa. Corporate domain users must be able
to use cluster resources (login as CORPORATE\user into a cluster node). If the cluster administrator can add
corporate domain accounts as cluster users, then this trust has likely been configured when the cluster domain
was created.
48
ANSYS Release 13.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.
Troubleshooting
If RSM jobs submitted to a Microsoft HPC cluster are failing for unknown reasons, you can gain additional
diagnostic information by running the HPC Job Manager (supplied as part of the Microsoft HPC Pack), selecting
the failed job, and examining the output section of the jobs tasks.
Depending on the installed version of Microsoft HPC, registry modification may be required to enable the
execution of commands via UNC paths. Special configuration is required if the task shows the following error:
UNC paths are not supported. Defaulting to Windows directory.
Input Error: Can not find script file "C:\Windows\MSCC_job.js".
To resolve this issue, create a text file of the following contents and save to a file (e.g. commandpromptUNC.reg)
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Microsoft\Command Processor]
"CompletionChar"=dword:00000009
"DefaultColor"=dword:00000000
"EnableExtensions"=dword:00000001
"DisableUNCCheck"=dword:00000001
Next, run the following command on the head node and all compute nodes in the cluster:
regedit -s commandpromptUNC.reg
The task of executing this on the compute nodes may be automated using the clusrun utility that is part
of the Microsoft HPC Pack installation.
ANSYS Release 13.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.
49
50
ANSYS Release 13.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.
The Compute Proxy settings in this example control the integration as follows:
Keyword
Currently supported keywords are LSFSSH, LSFRSH (LSF cluster via SSH and RSH, respectively), PBSSSH,
and PBSRSH (PBS cluster via SSH and RSH, respectively). Additional third-party job schedulers may be
integrated in the future.
Machine Name
A cluster node previously configured for password-less access via SSH or RSH.
Working Directory
The file-staging path. The RSM job creates a temporary directory here (for example, /staging/dh3h543j.djn). Mount this directory on all execution hosts so that the LSF/PBS job has access.
Custom1
For this example, this field is being used to specify local scratch space on the execution nodes. This path
must exist on all nodes. The LSF/PBS job script creates temporary directories in this location on all assigned
nodes using the LSF/PBS job ID (for example, /scratch/Job1234).
ANSYS Release 13.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.
51
Note
For a server test (...RSM\Config\scripts\TestServerUnixTP.cs), the queue is hardcoded to normal for LSF and workq for PBS. Also, the number of CPUs is set to 2. Edit this file
if these default settings are not appropriate.
Queue Creation
You must add the Compute Server to a new queue before submitting jobs from the client application (for
example, ANSYS Workbench). The name of the queue must match the name of the queue on the cluster.
2.
3.
4.
5.
6.
LSF Details
Shell scripts that are submitted to LSF are located in [RSMInstall]\Config\scripts. For a server test
the name is lsfjob_generic.sh. For an ANSYS Solver job the file is named lsfjob_ansys.sh. Any
52
ANSYS Release 13.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.
To monitor the job, the RSM job parses the output of the BJOBS command. Customize the default polling
frequency of 30 seconds in LSFUnixUtilities.cs.
PBS Details
Shell scripts that are submitted to PBS are located in [RSMInstall]\Config\scripts. For a server
test, the name is pbsJob_generic.sh. For an ANSYS Solver job, the file is named pbsJob_ansys.sh.
Any additional solvers that are supported follow the same convention. These shell scripts are actually a
generic base portion that is appended to a dynamically generated top portion resulting in a shell script for
a specific job (pbsJob.sh). The dynamic portion contains the variable values for the job, including number
of processors requested, input file names, scratch location, etc.
The following QSUB command is located in PBSUnixUtilities.cs. Customize the QSUB command as
needed.
string submitJobStr = string.Format("qsub -q {0}
-l select={1}:nCPUs={2}:mpiprocs={2}
-l place=scatter:excl -o stdout.out
-e stderr.out ./pbsJob.sh", queue, numberNodesRequested,
numProcs / numberNodesRequested);
To monitor the job, the RSM job parses the output of the QSTAT command. Customize the default polling
frequency of 30 seconds in PBSUnixUtilities.cs.
ANSYS Release 13.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.
53
54
ANSYS Release 13.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.
defining, 1
manually submitting jobs, 36
script customization, 35
job template, 35
Index
A
accounts, 2526
administration, 29
C
client application
defining, 1
file handling, 4
integration, 37
integration with Workbench, 37
supported solvers, 37
code template, 1, 35
Compute Proxy, 1, 4
Compute Server
adding a Compute Server, 30
Compute Server properties, 30
defining, 1
file handling, 4
remotely connecting to a Compute Server, 14
startup scripts, 11
testing, 32
configuring RSM, 8
Linux, 8
multi-user machines, 13
multiple network interface cards, 15
remote computing, 9, 14
starting Linux RSM services at boot time, 11
starting RSM services manually, 11
starting Windows RSM services at boot time, 8
startup scripts, 10
Windows, 8
Linux
configuration, 8
Explicit Dynamics systems, 13
installation, 7
native mode, 9
remote computing, 9
starting services at boot time, 11
startup scripts, 10
UNIX/Linux Path considerations, 13
LSF, 45, 51
M
mapped drives, 8
Microsoft HPC, 47
multi-user machines, 13
N
native mode, 9
Network File System, 4
O
overview, 1
P
passwords, 25
PBS Clusters, 51
EKM Servers, 11
Explicit Dynamics systems, 13
queue
creating, 29
defining, 1
file handling, 4
I
installing RSM, 7
prerequisites, 7
standalone installation, 7
uninstalling, 8
J
job
remote computing
configuration, 14
remotely connecting to a Compute Server, 14
remotely connecting to an RSM Manager, 14
RSH
integrating Windows with UNIX/Linux, 43
job limitations, 13
RSH/RCP configuration, 43
RSM Client
defining, 1
file handling, 4
ANSYS Release 13.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.
55
Index
RSM Manager
defining, 1
file handling, 4
remotely connecting to an RSM Manager, 14
solve manager properties, 30
startup scripts, 11
RSM user interface
Accounts dialog box, 22
context menu, 23
Desktop Alert dialog box, 22
List View, 17, 20
main window, 17
Menu Bar, 1718
Options dialog box, 21
Progress Pane, 17, 21
Status Bar, 17
system tray icon, 23
Toolbar, 17
Tree View, 17, 19
S
SSH
integrating Windows with UNIX/Linux, 39
job limitations, 13
selecting a remote computing mode, 9
SSH/SCP configuration, 39
startup scripts, 10
Compute Server, 11
EKM Servers, 11
RSM Manager, 11
T
terminology, 1
U
UNIX/Linux Path considerations, 13
user interface, 17
W
Windows
configuration, 8
installation, 7
integration with Platform LSF Cluster, 45
integration with UNIX/Linux using RSH/RCP, 43
integration with UNIX/Linux using SSH/SCP, 39
starting services at boot time, 8
uninstallation, 8
workflows, 2
56
ANSYS Release 13.0 - SAS IP, Inc. All rights reserved. - Contains proprietary and confidential information of ANSYS, Inc. and its subsidiaries and affiliates.