Give Now

M1 to M2 Transition

M1 to M2 Transition

For user currently using ManeFrame I (M1), below is a quick description of changes that will help with accessing and using ManeFrame II (M2) in addition to the full documentation.

Access

M2 uses SMU’s authentication system, which means that your username and password are from your SMU credentials. Your username is the first part of your SMU email address, i.e. "example" for "example@smu.edu", and your password is your SMU password. SMU’s password tool can be used to change or reset your password (https://pwreset.smu.edu), but remember that this changes your password for all SMU services such as email. The login nodes can be accessed at “m2.smu.edu”, e.g. "ssh example@m2.smu.edu". Additionally, there may be a lag of 30 to 60 seconds the first few times you log in.

Data

The storage systems for M1 and M2 are separate. Both have home and scratch directories, but they are different. Thus, any data that you’ll need on M2 needs to be copied from M1. Files can be moved as needed using standard tools such as “scp”, “rsync”, and SFTP clients. Additionally, SMU HPC administrators will be available to help users with the migration on Tuesdays and Thursdays at 10:00 AM in Fondren Science Building room 306A.

Applications and Toolchains

M2 uses the module system just like M1. “module avail” will show the available applications and compilers. Loading a compiler will show all software built using that particular compiler (“module load gcc-6.3; module avail”). We are now using Spack to install most open source software packages. Spack has several advantages over manual software building. Two principle advantages are automatic dependency resolution and reproducibility. You can see all the software currently built with Spack via “module load spack;  module avail”. Don’t hesitate to let me know if you’d like something additionally installed.

Running Jobs

M2 uses Slurm just like M2 so the job submission process is nearly identical. The most significant difference are the queues (partitions), which are outlined here and viewable on M2 via “sinfo”. Like M1, the M2 queues are delineated by resource type and the maximum job run time. There are example submit scripts for a few applications in /hpc/examples/.

Please don’t hesitate to let us know at smuhpc-admins@smu.edu if you have any problems or questions. In addition, the full documentation can be found here.

Transferring Data from ManeFrame (M1) to ManeFrame II (M2) Using Globus

  1. Obtain your SMU Certificate Subject DN
    1. Go to URL: https://cilogon.org/ and Select “Southern Methodist University” as the Identity Provider in the selection box. Then Click “Log On” to continue.
    1. Next you will be redirected to SMU’s “IdP” page to authenticate against your SMU credentials. Please use your SMUID and Password to authenticate.
    1. Upon successful authentication, you will be redirected to a webpage displaying your “Certificate Subject”. As show in screenshot-3 below
    2. Please copy your certificate subject line, for example /DC=org/DC=cilogon/C=US/O=Southern Methodist University/CN=<Your Name followed by a code>.
    1. Send an email with the copied Certificate Subject line to help@smu.edu with the following subject line: “HPC Globus Data Transfer Access”
    2. Once you email your Certificate Subject DN we will give permission to your account to being transfers using Globus online tool.
  2. Signup at Globus.org
    1. Go to URL: https://globus.org Click on “Log In”
    1. You will be prompted to use your existing organizational login. From the dropdown select “Southern Methodist University”, then continue.
    1. You will then be redirected to SMU IdP page to authenticate with your SMUID and Password. Provide your credentials and login.
    1. Upon successful authentication, you will be prompted to Link to an existing Globus Account. In most cases we will Select/Click “no thanks, continue”. NOTE: If you already have a Globus account/ID and prefer to link it with your SMUID then click link to existing account and follow the screens to do so. If not then don’t bother and continue by clicking “no thanks, continue”.

    1. On next webpage you will be prompted with information on how Globus is going to use the identities shared by SMU. Safely select “Allow”, as this is required for data transfers to work.
    1. This completes the signup process and now you login screen should look similar to that shown below.
  3. Initiate Data Transfer
    1. Once logged in, you will see a webpage with two drag and drop windows to initiate transfers. Globus calls source and destination of a file transfer as “Endpoint”.
    2. To begin transfer between M1 scratch (ManeFrame I cluster) and M2 scratch (ManeFrame II cluster):
    3. Begin typing in the Left Endpoint text box: SMU_M1_data_transfer_node_endpoint A popup window will display the endpoint matching the string entered, select that.
    1. You should now see the directories from /scratch/users on M1 on your left.