User Environment

A. Account Creation

1. Researchers that have been approved to use the Nurion system should access the KSC website (https://www.ksc.re.kr) to apply for an account.

1) How to apply : Access the KISTI website, (top) Application for use -> (top) Apply -> Select application

• Free account : Nurion system innovative support program, new users of the 5th supercomputer

• Paid account : General and student users of the 5th supercomputer

• Once an account has been created, information related to the account will be sent to the email listed on the application.

2) Request for OTP (One Time Password) authentication code

Based on the account information email you have received, send an email to [e-mail] by referring to the example below to receive an authentication code.

Subject	Request for an OTP authentication code – user ID
Recipient	(example) Request for an OTP authentication code - x123abc
Email Body (example)	[e-mail]

3) Installing OTP application

• The OTP smartphone application is provided for secured access to the supercomputer.

• For the OTP smartphone application, search for “Any OTP” on Google Play or App Store and install the application developed by Mirae-tech.

• When logging into the supercomputer, the OTP security code of the “Any OTP” application must be entered.

  • If you do not use a smartphone, please consult the account manager ([e-mail]).

  • Refer to the “OTP User Manual” by accessing the KISTI website > Technical Support > Guidelines for more details on OTP installation and use

    • Emails will be sent out for users on the LG U+ network because text messages are processed as spam on this network

B. Login

• Users can gain access through the login node (nurion.ksc.re.kr) of the Nurion system (refer to the node configuration below).

  • By logging into MyKSC (KISTI Supercomputer Web Service Portal, https://my.ksc.re.kr) via a web browser, users can utilize GUI-based HPC and AI/data analysis services (refer to the MyKSC guide for instructions)

• Default character set (encoding) is in unicode (UTF-8).

• Only ssh, scp, sftp, and X11 are allowed to access the login node.

1. Unix or Linux environment

$ ssh -l <USER_ID> nurion.ksc.re.kr [-p 22]

• e.g.) When user ID is x123abc

$ ssh -l x123abc nurion.ksc.re.kr
or
$ ssh -l x123abc nurion.ksc.re.kr -p 22

2. Windows environment

• Run Xming to execute the X environment

  • Download the program for free from the internet and install it.

• Use ssh access programs such as PuTTY or SSH Secure Shell Client

  • Host Name : nurion.ksc.re.kr, Port : 22, Connection type : SSH

  • Programs can be downloaded for free from the internet.

• ssh -> X11 tap -> check "Enable X11 forwarding"

• X display location : localhost:0.0

※ If the system cannot be accessed because of a DNS caching problem, clear all cache (run ipconfig/flushdns in command prompt) and access again.

C: ipconfig /flushdns

3. Sending/receiving files

• Files can be transferred to and from the Datamover node (nurion-dm.ksc.re.kr) using an FTP client via FTP or SFTP (refer to the node configuration below).

$ ftp nurion-dm.ksc.re.kr 
or 
$ sftp [user ID@] nurion-dm.ksc.re.kr [-p 22]

• In the Windows environment, use FTP/SFTP client programs such as WinSCP that are distributed for free to access the system.

• When using FTP (File Transfer Protocol), file transfers can be made without entering an OTP.

• When using SFTP (Secure FTP), it is required to enter OTP for file transfers. (SFTP is a more secure transfer method than FTP)

4. Node configuration

• It is recommended to use the Datamover node, which has no CPU limit, for downloading via wget or git and for transferring large datasets (transfers on the login node may be interrupted due to CPU limits).

• File compression and decompression may also be interrupted due to CPU limits. If processes are forcibly stopped on the login node, perform compression/decompression on the Datamover node.

C. Changing User Shell

• BASH is provided as the default shell for the login node of the Nurion system. The chsh command is used for changing to a different shell.

$ chsh

• echo $SHELL is used for checking the currently used shell.

$ echo $SHELL

• Change the configuration files (.bashrc, .cshrc, etc.) in the home directory of a user

D. Changing User Password

• Use the passwd command in the login node to change a user’s password.

$ passwd

• Password-related security policy

  • The user password must be at least 9 characters and include an alphabet, number, and special character. English words in the dictionary cannot be used.

  • The user password expiration period is two months (60 days).

  • The new password cannot be the same as the five previously used passwords.

  • Maximum number of incorrect login attempts : 5

    • The ID will get locked if you attempt to log in five times with the incorrect password; contact the account manager ([e-mail]) when your account is locked.

    • The IP address of a PC will be temporarily blocked if you attempt to log in five times with the incorrect password; contact the account manager ([e-mail]) if needed.

  • Maximum number of incorrect OTP authentication attempts : 5

    • Contact the account manager ([e-mail]) if you have failed to authenticate five times.

E. Checking SRU Time Usage of User Account

• Access the integrated supercomputer account managing system (ISAM) to check a user’s contract information, detailed batch job usage, and total SRU time usage.

$ isam

F. Job Directory and Quarter Policy

• Users are provided with two file systems: a home directory (/home01/$USER) and a scratch directory (/scratch/$USER).

• The home directory has limited capacity and I/O performance; thus, all computation jobs must be executed in a user’s work space of /scratch, which is the scratch directory.

• A user’s current usage can be checked with the following commands.

$ lfs quota -h /home01
$ lfs quota -h /scratch

• A user’s job directory is applied to different policies according to use.

• The file deletion policy(scratch purge policy) is applied based on the access time (atime) of the file attributes.

  • atime(Access timestampe): the last time the file was accessed.

  • mtime(Modified timestampe): the last time the file's content was modified.

  • ctime (Change timestamp): the inode modification time due to changes in file permissions, ownership, links, etc.

※ In the existing purge policy (files that have not been accessed for 15 days are automatically deleted), recovery of deleted files is basically impossible, but some changes are made to the purge policy to provide a grace period for users who forget to manage files. (2023.05. applied)

• After the purge policy is executed, the target file is prefixed with ToBeDelete_. e.g.) ToBeDelete_file1.txt, ToBeDelete_file2.txt

  • If target file is needed, user must directly recover prefixed filename and update atime.

• After a certain period of time (20 to 30 days), files marked with ToBeDelete_ will be deleted in bulk, and the files cannot be recovered.

• atime can be checked with stat, ls -lu command, etc.

[login01 ~]# stat file1
File: ‘file1’
Size: 0 Blocks: 0 IO Block: 4096 regular empty file
Device: 805h/2053d Inode: 3221237903 Links: 1
Access: (0644/-rw-r--r--) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 2022-04-05 08:52:30.113048319 +0900
Modify: 2022-04-05 08:52:30.113048319 +0900
Change: 2022-04-05 08:52:30.113048319 +0900

$ ls -lu test.file
-rw-r--r-- 1 testuser testgroup 58 Jan 1 17:06  test.file

Last updated on November 07, 2024.