This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
hpc_onboarding_guide [2026/05/13 12:04] bdepaula created |
hpc_onboarding_guide [2026/05/13 12:29] (current) bdepaula [Fugaku Account Application System (FAAS)] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== HPC Onboarding Guide ====== | ====== HPC Onboarding Guide ====== | ||
| - | This page describes instructions for obtaining credentials to different HPC clusters. It includes tips for the onboarding process, and other tricks | + | This page summarizes |
| ===== RIKEN Fugaku ===== | ===== RIKEN Fugaku ===== | ||
| - | For both RIKEN' | + | Access to both Fugaku and Miyabi |
| - | It is important to note that you will be asked for identification documents, and also for a company ID. The company ID is the BSC identification card (used at the doors and turnstiles in our buildings). **You must provide the photo of the front and back of your card**, even if the back is blank. Try to take a photo so they see it is the same card (maybe showing the lanyard). | + | https://www.hpci-office.jp/ |
| - | Also important | + | You can create an HPCI account before being assigned |
| - | Their page may read as if you can use a Spanish driver' | + | During registration |
| + | | ||
| + | | ||
| - | Upon completing | + | For BSC users, |
| - | The PI of the project or someone from RIKEN will contact you asking for your HPCI ID and Verification code. Give that to them, and wait for their confirmation. | + | Your name must exactly match the format used in your BSC card: |
| + | * Use uppercase letters | ||
| + | * Preserve the same order of names and surnames | ||
| - | You will have to complete now the process at the FAAS (Fugaku Access Account System): https:// | + | Failure to do so will usually result |
| - | The process includes several steps, and there are " | + | Although |
| + | ==== Fugaku Account Application System (FAAS) ==== | ||
| + | After completing the HPCI registration, | ||
| + | * An HPCI User ID (e.g. '' | ||
| + | * A Verification Code | ||
| - | Once your account is approved, you will receive a certificate (e.g., | + | 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:// | ||
| + | |||
| + | 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 | ||
| + | |||
| + | {{: | ||
| + | |||
| + | Approval may take from one day to several weeks. | ||
| + | |||
| + | |||
| + | ==== Browser User Certificate ==== | ||
| + | |||
| + | After approval, you will receive a browser certificate (e.g. '' | ||
| + | |||
| + | 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:// | ||
| + | * Fugaku OnDemand: | ||
| + | https:// | ||
| + | * Fugaku website: | ||
| + | https:// | ||
| + | |||
| + | ==== 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: | ||
| + | |||
| + | < | ||
| + | Host fugaku | ||
| + | HostName login.fugaku.r-ccs.riken.jp | ||
| + | User u1*** | ||
| + | IdentityFile ~/ | ||
| + | </ | ||
| + | |||
| + | ==== Batch Scheduler ==== | ||
| + | |||
| + | Fugaku uses Fujitsu' | ||
| + | |||
| + | 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: | ||
| + | #PJM -L rscgrp=small | ||
| + | #PJM -g ra1***** | ||
| + | |||
| + | hostname | ||
| + | </ | ||
| + | |||
| + | Submit the job with: | ||
| + | |||
| + | <code bash> | ||
| + | pjsub --no-check-directory job.sh | ||
| + | </ | ||
| + | |||
| + | Check resources with: | ||
| + | |||
| + | <code bash> | ||
| + | pjshowrsc --rg | ||
| + | </ | ||