HFSS15: Installation of ANSYS EM Tools on SGE

Windows:

Install on every node of cluster

Setup ‘temp directory’ to a path that is same on all nodes. For example, c:temp

LINUX:

Install on a single node, on a shared drive.

Setup ‘temp directory’ to a path that is same on all nodes. For example, /tmp

Ensure that the product is available using the same path on all nodes

Permissions:

All users of the cluster should have read/write permissions to temp directory

All users should have read/execute permissions to installation directory

When a desktop scheduler GUI is run the same node as the job submission node, no other configuration is necessary: installation is sufficient. You select the scheduler through the desktop GUI. You need to ensure that scheduler commands are available in the path before you launch desktop.

Turn OFF firewall between cluster nodes.

Scenario 1: The post-processing node and job-submission node roles are served by distinct machines.

In this case, perform the following configuration:

The job-submission node should be configured to run Ansoft RSM service, which serves as a proxy to scheduler. The Ansoft RSM Service should be running as 'root' in order to facilitate jobs running using the credentials of the job's owner. A configuration file in the RSM installation folder should be edited to specify information regarding the scheduler that manages jobs on this cluster. A block labeled 'Scheduler' must be included within the 'AnsoftCOMDaemon' block. This block contains two string entries:

• SchedulerName: this contains the unique part of the scheduler proxy library name

• ConfigString: this contains a scheduler specific configuration string

The case of the SchedulerName string is significant on Linux because Linux file names are case sensitive. The case of the SchedulerName string is not significant on Microsoft Windows. In R14.5, the possible scheduler names are: lsf and sge. The ConfigString entry is a scheduler specific configuration string, described below.

In addition, the AnsoftRSMService must be started with appropriate environment variables set. Generally, the environment variables must be set the same as they would be set for using the scheduler via command lines.

SGE Details

For SGE, the ConfigString entry must contain the search path for the SGE commands. It may contain a single directory, the directory containing the SGE commands. Alternatively, it may be a path, with directories separated by the colon character ":", where the SGE command directory appears before any other directory containing files with the same name as any SGE commands.

Example ansoftrsmservice.cfg configuration file:

$begin 'AnsoftCOMDaemon'

$begin 'Managed COM Servers'

$end 'Managed COM Servers'

$begin 'Scheduler'

'SchedulerName'='sge'

'ConfigString'='/opt/sge6.2u4/bin/lx24-amd64'

$end 'Scheduler'

$end 'AnsoftCOMDaemon'

Scenario 2: The post-processing node and job-submission node roles are served by the same machine.

The Select Scheduler... command (as described in the Job Management User Interface for SGE section) is used to gather details about the scheduler. In this case, the Desktop process should be started in an environment suitable for submitting jobs to the scheduler.

The environment should be configured so that all SGE commands are found using the standard search path. In particular, search for the following commands in the search path should result in the SGE command being found: "qsub", "qdel", "qstat", and "qconf". No other command with the same name should appear before the SGE command in the search path.

Related Topic

Job Management User Interface for SGE

Command Line Enhancements for Ansoft Desktop Products