You are on page 1of 14

Migrating to RSM 16.

0

Configuration Changes and Examples

1

© 2014 ANSYS, Inc.

January 6, 2015

ANSYS Confidential

Inc. These changes enable RSM to handle more of the secure configurations commonly requested by customers when running in service mode. January 6.0 of ANSYS Remote Solve Manager has a number of configuration changes relating to file permissions.0. • Release 16. • This document describes the changes that you need to be aware of in Release 16. • Two configuration examples are included that showcase the new functionality. 2015 ANSYS Confidential .Introduction 2 © 2014 ANSYS.

• This did not fit the security and file quota requirements of many computing environments.Previous Issue: Open File Permissions Client Solve Manager Open file permissions 3 Compute Server Open file permissions • In pre-16.0 versions of RSM. © 2014 ANSYS. 2015 ANSYS Confidential . January 6. it was required that all users have access to a folder in a multi-user environment. Inc.

January 6. the permissions stay with the user. 2015 ANSYS Confidential .0. Inc. © 2014 ANSYS. • Therefore. the User Proxy (UP) is used to transfer files instead of the RSM service(s).Solution: The User Proxy Client UP Solve Manager Compute Server UP UP Stays under user permissions throughout workflow 4 • In RSM 16.

• Changes to alternate account setup • Extra firewall configuration • Changes to RSM configuration to allow for “secure” configuration • Configuration changes to OS file transfer mechanism for users in a “secure” configuration January 6.Implications for Configuration 5 © 2014 ANSYS. 2015 ANSYS Confidential . Inc.

January 6. Inc. 2015 ANSYS Confidential . • The alternate account assigned to localhost is also the account that is used for User Proxy file transfer from Client to Solve Manager. • Therefore.Alternate Account Setup 6 © 2014 ANSYS. even if it will not be used as a compute server. • The alternate account now has an extra role because of the User Proxy workflow. if the remote Manager has a different account than the Client account. you must assign an alternate account to that “manager (localhost)”.

2015 ANSYS Confidential .Firewall Configuration • Ans. January 6.Rsm.Rsm.SHHost.JMHost.UPHost.exe – 9160 • Ans.exe – dynamic port allocation (both client & server) 7 © 2014 ANSYS.Rsm. Inc.exe – 8160 • Ans.

8 © 2014 ANSYS. January 6.config .AppSettings.RSM.Rsm.AppSettings. Inc. • User Proxy uses dynamic ports by default. you could specify a port range of 1000-2000. this is what is shown in the example below.config file.Restricting/Changing the Default Ports and Dynamic Port Ranges • Configuration options from various files have been amalgamated into one new Ans. Since this is most likely what will need to be changed.Edit the following line in the relevant section: <add key="PortRange" value=“" /> For example.Rsm. • If you want to restrict/change the UP port range: .config Linux: \ansys_inc\v160\RSM\Config\Ans.Open the following file in a text editor: Windows: \Ansys Inc\v160\RSM\Config\Ans. 2015 ANSYS Confidential . This value should be enough to cover the number of users.AppSettings.

January 6. you will need to change the way you set up network shares (especially if using Samba).0 or earlier. • If you are using a secure share method (such as a user’s home directory). 2015 ANSYS Confidential .Configuration Changes to OS File Transfer 9 • If you are using a group share method (such as a shared drive with open permissions).1. Refer to section 2.4. Inc. Operating System File Transfer Utilizing Network Shares in the RSM User’s Guide for more information. no changes are needed to your setup from R15. © 2014 ANSYS.

January 6. such as a link to their $HOME. Inc.Environment Variables Allowed in RSM Interface 10 • User Proxy also enables us to have the correct user expand those variables before file transfer. • Administrators can add variables that would be expanded by users. © 2014 ANSYS. • This means shared directories can now be a thing of the past. 2015 ANSYS Confidential .

January 6. Inc. 2015 ANSYS Confidential .0 Configuration Examples 11 © 2014 ANSYS.RSM 16.

12 © 2014 ANSYS. Inc. January 6. If you are using a group share method (such as a shared drive with open permissions).0. 2015 ANSYS Confidential . you do not need to make any changes to your setup from R15.0 or earlier.Important The following examples pertain to new functionality that was not available prior to Release 16.

Example 1: Using Per-user Linux HOME Directories for the Project and Shared Cluster Directories • It is recommended that you have a separate “rsmtemp” directory under each HOME for storing temporary files. Inc. where %H stands for the HOME directory. 13 © 2014 ANSYS. you will need to configure Samba. 2015 ANSYS Confidential . January 6. • A sample Samba configuration for RSM_MGR and RSM_CS is shown below. • If doing Windows -> Linux file transfers.

Example 2: Using a Shared Drive with User-specific Folders • It is recommended that you have a separate directory under each HOME for storing temporary files (in this case called rsmJobs). Inc. 2015 ANSYS Confidential . • A sample Samba configuration for RSM_MGR and RSM_CS is shown below. where the %u path variable represents a user’s username. January 6. • If doing Windows -> Linux file transfers you will need to configure Samba. 14 © 2014 ANSYS.