Skip to content
Home > Access resource > Using archer2 > Applying for project…

Applying for project membership

[et_pb_section fb_built=”1″ _builder_version=”4.20.2″ _module_preset=”default” global_colors_info=”{}”][et_pb_row _builder_version=”4.20.4″ _module_preset=”default” global_colors_info=”{}”][et_pb_column type=”4_4″ _builder_version=”4.20.4″ _module_preset=”default” global_colors_info=”{}”][et_pb_text _builder_version=”4.23.1″ _module_preset=”default” hover_enabled=”0″ global_colors_info=”{}” sticky_enabled=”0″]

Applying for project membership

Following a successful application for ARCHER2 resource, via the HEC-WSI, the first thing you must do, before you can access the resource, is to join the HEC-WSI project on the SAFE system. NOTE: it makes sense to complete this process on the computer you intend to use to access ARCHER2 (as you will need to upload a file generated on that computer.

Step 1   Create a SAFE account (if you have not already) and log on to SAFE

Step 2   Go to the ‘Projects’ tab and select ‘Request access’

Step 3   On the ‘Apply for project membership’ page, select the project for which you wish to request access (all HEC-WSI-supported projects are under the HEC-WSI project, e773)

Step 4   On the following ‘Apply for project membership’ page, check the project is correct (i.e. e773 for the HEC-WSI project). NOTE: the ‘access route’ defaults to ‘Request machine account’. Select ‘Apply’

Step 5   On the SAFE Login account Request’ page check the project is correct (i.e. e773 – HEC WSI). Select the ‘Machine’ you wish to access. NOTE: the HEC-WSI project is restricted to the archer2 machine so ensure that the ‘archer2’ machine is selected and click ‘Next’

Step 6   You’ll then need to complete the ‘SAFE Login account Request’.

– Add a username

– Confirm that you accept the Terms and Conditions of Access

– You’ll then need to add an ‘SSH public key’. For instructions on how to add an SSH public key: [read more]

  1. The key must be generated on the computer that will be used to access ARCHER2.
  2. Refer to the ARCHER2 User Documentation – Quick-start for users. Section on ‘Generating and adding an SSH key pair’.
  3. Follow link to ARCHER2 User and Best Practice Guide and go to the section on ‘SSH Key Pairs’
  4. Using a terminal (the command line), on the machine you wish to use to access ARCHER2, navigate to the default location for ssh keys on your local system (usually ~/.ssh/ on LINUX), type the following, remembering to replace “your@email.com” with your e-mail address: 
    ssh-keygen -t rsa -C “your@email.com”
  5. You will be asked to ‘Enter file name to save the key’ (I used SSHKey).
  6. You’ll also be asked to ‘Enter a passphrase’ that you’ll use to unlock the key (NOTE: you can leave this empty to have no passphrase, but this is not recommended)
  7. You will then see the ‘key fingerprint’ printed out to the terminal. A text file (e.g. SSHKey) and a .pub file (e.g. SSHKey.pub) will have been generated in the current location. NOTE: if you have not generated these files directly within the default location for ssh keys on your local system (usually ~/.ssh/ on LINUX) you may wish to move them there now as this will simplify logging onto the system in the future.
  8. Upload the file generated, e.g. SSHKey.pub, into the ‘SAFE Login account Request’ form.
  9. Click ‘Request’ [/read]

Step 7   Set a Multi-Factor Authentication (MFA) token for your account. As of December 2023, instead of your ARCHER2 password, a Time-based One-Time Password (TOTP) code will be requested. This is a six digit number, refreshed every 30 seconds, which is generated typically by an app running on your mobile phone or laptop. Thus authentication will require two factors, i.e. SSH key and passphrase (the first factor), plus TOTP (the second factor). The SAFE documentation includes details on how to set up MFA on machine accounts (ARCHER2).

Step 8   Await approval. Once the HEC-WSI Support Team have received your request, and ensured your details are consistent and correct, your application will be approved. This will give you access to the HEC-WSI project (e773) on SAFE (which has zero CUs allocated to it).

Step 9   The HEC-WSI Support Team will create a sub-group for your specific allocation, e.g. e773-PB-0101, and allocate the awarded resource. You, and additional members (specified in your application for HEC-WSI resources), will be added to this sub-group.

Step 10   If you wish to add additional members (not declared on your original application) to your sub-group you must contact the HEC-WSI Support Team, with details of the additional members and confirmation of their nationalities, before their project membership can be approved.

Next: Connecting to ARCHER2

[/et_pb_text][/et_pb_column][/et_pb_row][/et_pb_section]

Team member