start:mogon_cluster:access

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
start:mogon_cluster:access [2020/09/08 17:52]
jrutte02 [Access] LOL
start:mogon_cluster:access [2021/03/18 14:14] (current)
jrutte02 [Access]
Line 11: Line 11:
 ===== Access ===== ===== Access =====
  
-<grid> 
-<col lg="6" md="12" sm="12" xs="12"> 
 <callout type="tip" title="Remote Access" icon="true"> <callout type="tip" title="Remote Access" icon="true">
 Since the MOGON clusters are Linux-based systems, remote access is granted via ''SSH''. Since the MOGON clusters are Linux-based systems, remote access is granted via ''SSH''.
Line 19: Line 17:
 **[[:start:mogon_cluster:access_from_outside_unix|access MOGON using Linux/macOS]] / [[:start:mogon_cluster:access_from_outside_windows|access MOGON using Windows]]**. The latter link contains information for accessing MOGON with ''PuTTY'', ''MobaXterm'' and ''PowerShell''. **[[:start:mogon_cluster:access_from_outside_unix|access MOGON using Linux/macOS]] / [[:start:mogon_cluster:access_from_outside_windows|access MOGON using Windows]]**. The latter link contains information for accessing MOGON with ''PuTTY'', ''MobaXterm'' and ''PowerShell''.
  
-Login to the login-nodes is mediated by a jump node: Access is done with direct login (ssh) to <nowiki>"</nowiki>''mogon''<nowiki>"</nowiki>. This name implements a ''Round-Robin-DNS'' login to both login nodes of **MOGON I**''mil01.zdv.uni-mainz.de'' and ''mil02.zdv.uni-mainz.de''If for some reason you want to login to a specific login node, you can use these names directly. (or if for some other reason one of the nodes is broken, and the DNS always gives you the wrong, broken one to connect to)+The login nodes of **MOGON II** are ''miil01.zdv.uni-mainz.de'' to ''miil03.zdv.uni-mainz.de''
  
-The login nodes of **MOGON II** are ''miil01.zdv.uni-mainz.de'' to ''miil03.zdv.uni-mainz.de''. Projects on MOGON I do not have access to MOGON II automatically. You have to apply for MOGON I and MOGON II separately. + 
 +<grid> 
 +<col lg="6" md="6" sm="6" xs="12">
 <callout type="danger" title="Login" icon="true"> <callout type="danger" title="Login" icon="true">
 Only password-less login is available. Only password-less login is available.
 </callout> </callout>
 </col> </col>
-<col lg="6" md="12" sm="12" xs="12"> +<col lg="6" md="6" sm="6" xs="12"> 
-<callout color="#c1002a" icon="fa fa-power-off" title="MOGON I End Of Life"> +<callout type="warning" icon="true" title="SSH-Key"> 
-MOGON I will be shut down at 31th September 2020+You **need to have your SSH-Key** uploaded on [[https://account.uni-mainz.de/sshkey|account.uni-mainz.de/sshkey]] to be able to log in to MOGON((A neat overview on ssh-keys and how to generate and copy them can be found [[https://www.ssh.com/ssh/copy-id|here]]. Or you can follow our [[start:mogon_cluster:access#how_to_set_up_ssh-keys_for_mogon|guideline]])). 
 + 
 +Your SSH-Key is automatically added to the MOGON cluster. Would You Like To Know More? Read this [[start:mogon_cluster:basic_authentication#add_ssh-key_to_mogon|Article]]!
 </callout> </callout>
 +</col>
 +
 +</grid>
 +
 +
 === MOGON Service Nodes Overiew === === MOGON Service Nodes Overiew ===
 <datatable info="false" paging="false" searching="false"> <datatable info="false" paging="false" searching="false">
-^ Service Node ^ FQDN ^ Cluster ^ Description^ +^ Service Node ^ FQDN ^ Description^ Fingerprint 
-| ''login21'' | ''miil01.zdv.uni-mainz.de'' | MOGON II | Login Node | +| ''login21'' | ''miil01.zdv.uni-mainz.de'' | Login Node | MD5:''a6:a1:d2:13:df:2b:59:91:2f:e1:a5:50:1c:f1:b0:b4'' \\ SHA256:''eu8N17/EHw0pwvUVT6Htm7yek54t8s8QdRN+A92sjek''   
-| ''login22'' | ''miil02.zdv.uni-mainz.de'' | MOGON II | Login Node | +| ''login22'' | ''miil02.zdv.uni-mainz.de'' | Login Node | MD5:''3d:90:0e:fa:ce:b1:db:6d:22:ff:6c:94:d0:fe:2d:34'' \\ SHA256:''WcJllAYU8qNcm31WLeg892JHbuczesfWVM5bTmtaisA''
-''login23'' ''miil03.zdv.uni-mainz.de'' | MOGON II | Login Node +| ''login23'' | ''miil03.zdv.uni-mainz.de'' | Login Node | MD5:''dc:e7:9f:c9:3b:13:cc:3a:65:ce:15:5d:8d:b1:9b:71'' \\ SHA256:''v5wiJI/jBTqpYF/g07VMH7WVesbVaovYTcT/MpgcWhc''
-| ''login01'' | ''mil01.zdv.uni-mainz.de'' | MOGON I | Login Node | +| ''hpcgate'' | ''hpcgate.zdv.uni-mainz.de'' | Jump Host | MD5:''63:67:65:76:5f:ad:fb:20:f2:68:92:cf:d5:49:2c:dc'' \\ SHA256:''CNbkj04hEuJ9IwgGkTBXbF1WtE/Nb46kPVSejKUGfRU'' |
-''login02'' ''mil02.zdv.uni-mainz.de'' | MOGON I | Login Node +
-| ''hpcgate'' | ''hpcgate.zdv.uni-mainz.de'' | MOGON | Jump Host |+
 </datatable> </datatable>
 <callout type="info" icon="true" title="Service-Node FQDN"> <callout type="info" icon="true" title="Service-Node FQDN">
 If you access MOGON Service-Nodes through the ''HPCGATE'' you can omit ''zdv.uni-mainz.de'', e.g.: for ''login21'' ''miil01'' is sufficient. If you access MOGON Service-Nodes through the ''HPCGATE'' you can omit ''zdv.uni-mainz.de'', e.g.: for ''login21'' ''miil01'' is sufficient.
-</callout> 
-</col> 
-</grid> 
- 
- 
-<callout type="warning" icon="true" title="SSH-Key"> 
-You **need to have your SSH-Key** uploaded on [[https://account.uni-mainz.de/sshkey|account.uni-mainz.de/sshkey]] to be able to log in to MOGON((A neat overview on ssh-keys and how to generate and copy them can be found [[https://www.ssh.com/ssh/copy-id|here]]. Or you can follow our [[start:mogon_cluster:access#how_to_set_up_ssh-keys_for_mogon|guideline]])). 
- 
-Your SSH-Key is automatically added to the MOGON clusters. Would You Like To Know More? Read this [[start:mogon_cluster:basic_authentication#add_ssh-key_to_mogon|Article]]! 
 </callout> </callout>
  
Line 74: Line 70:
 <code>Enter a file in which to save the key (/home/you/.ssh/id_rsa): [Press enter] </code> <code>Enter a file in which to save the key (/home/you/.ssh/id_rsa): [Press enter] </code>
  
-After that you have to specify a passphrase - {{fa>warning?fw}} **Do not** use an empty passphrase! {{fa>warning?fw}}+After that you have to specify a passphrase - {{fa>warning?fw}} **use passphrase!** {{fa>warning?fw}}. An empty passphrase is a serious security concern. 
  
 <code bash>Enter passphrase (empty for no passphrase): [Type a passphrase] <code bash>Enter passphrase (empty for no passphrase): [Type a passphrase]
  • start/mogon_cluster/access.1599580357.txt.gz
  • Last modified: 2020/09/08 17:52
  • by jrutte02