hpc_onboarding_guide []

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== HPC Onboarding Guide ======

This page summarizes the onboarding process for several HPC systems, including common pitfalls and recommendations to avoid delays with support teams.

===== RIKEN Fugaku =====

Access to both Fugaku and Miyabi requires an account in the Japanese High Performance Computing Infrastructure (HPCI):

https://www.hpci-office.jp/

You can create an HPCI account before being assigned to a project, so it is recommended to start this process as early as possible.

During registration you will be asked for:
  * Personal identification documents
  * A company ID

For BSC users, the company ID is the BSC access card used at the building entrances. Upload photos of both the front and back of the card, even if the back is blank.

Your name must exactly match the format used in your BSC card:
  * Use uppercase letters
  * Preserve the same order of names and surnames

Failure to do so will usually result in rejection and significant delays.

Although the HPCI documentation may suggest that a TIE or Spanish driver's license is sufficient, in practice they usually request the passport. Uploading both TIE and passport from the beginning is recommended.

==== Fugaku Account Application System (FAAS) ====

After completing the HPCI registration, you will receive:
  * An HPCI User ID (e.g. ''hpci1234'')
  * A Verification Code

Keep the Verification Code, as it will be required later for both Fugaku and Miyabi onboarding.

Your project PI or a RIKEN contact will ask for:
  * Your HPCI User ID
  * Your Verification Code

Continue the process through FAAS:

https://apply.fugaku.r-ccs.riken.jp/login

Create an account and complete all onboarding steps. You will again be asked to upload:
  * Personal identification
  * BSC identification card

Common reasons for rejection include:
  * Passport missing
  * Name mismatch
  * Missing back side of ID cards
  * Low-quality photos

The FAAS interface displays onboarding steps as colored dots:
  * Orange: action required
  * Green: completed
  * Grey: pending review or inactive

{{:faas_fugaku.png?600 |}}

Approval may take from one day to several weeks.


==== Browser User Certificate ====

After approval, you will receive a browser certificate (e.g. ''u1234.p12'').

FAAS also provides a PDF containing the certificate passphrase. Store both securely.

Import the certificate into your browser, for example in Firefox:

  Preferences → Privacy & Security → Certificates → View Certificates → Import

The certificate is required to access:
  * User Portal:
    https://www.fugaku.r-ccs.riken.jp/user_portal/
  * Fugaku OnDemand:
    https://ondemand.fugaku.r-ccs.riken.jp/pun/sys/dashboard
  * Fugaku website:
    https://www.fugaku.r-ccs.riken.jp/en/

==== SSH Keys ====

Fugaku explicitly forbids adding SSH keys directly on login nodes. Doing so may result in account suspension.

Only use SSH keys uploaded through the Fugaku User Portal.

If GitHub or GitLab access is required, use SSH forwarding instead of copying keys to the system.

Example SSH configuration:

<code>
Host fugaku
    HostName login.fugaku.r-ccs.riken.jp
    User u1***
    IdentityFile ~/.ssh/id_rsa
</code>

==== Batch Scheduler ====

Fugaku uses Fujitsu's PJM implementation, part of the ''Fujitsu Technical Computing Suite (TCS)''.

Autosubmit supports this PJM version. Fugaku also provides a smaller Slurm environment mainly associated with GPU resources.

Example PJM batch job:

<code bash>
#!/bin/bash

#PJM -N test_job
#PJM -L elapse=00:02:00
#PJM -L rscgrp=small
#PJM -g ra1*****

hostname
</code>

Submit the job with:

<code bash>
pjsub --no-check-directory job.sh
</code>

Check resources with:

<code bash>
pjshowrsc --rg
</code>
User Tools

Site Tools

Page Tools
