Changes between Version 19 and Version 20 of User Guide/Remote Access
- Timestamp:
- Nov 21, 2024, 5:17:56 PM (13 days ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
User Guide/Remote Access
v19 v20 2 2 == Remote Access 3 3 4 === To User account and Files 5 Users with an account can always access their Home Directories, and files, and run basic scripts, by SSH and connecting to {{{ ssh YOUR_USERNAME@gw.cosmos-lab.org }}}. Detailed instructions are available at: [wiki:./Console Connecting to a console page]. 4 === Access to User Account and Files 5 Users without a reservation can always access their account's home directories, files, and BASH scripts through SSH by connecting to: \\ 6 {{{#!div style="font-size: 100%" 7 {{{#!shell 8 ssh USERNAME@gw.cosmos-lab.org 9 }}} 10 }}} 11 === Access to Consoles 12 The [wiki:UserGuide/RemoteAccess/Console domain consoles] can be accessed the same way as the gateway (above), with the following differences: 13 {{{#!div style="font-size: 100%" 14 {{{#!shell 15 ssh USERNAME@console.DOMAIN.cosmos-lab.org 16 }}} 17 }}} 18 * Consoles can '''ONLY''' be connected to a current (and approved) [wiki:GettingStarted#MakeaReservation reservation]. 19 * In addition to home directories access and computing/running scripts, consoles can run [http://omf.orbit-lab.org OMF] commands to [wiki:Resources control resources] within their [wiki:Architecture/Domains domain]. 20 * Consoles share a [wiki:Architecture/Network#ControlPlane Control Network] with [wiki:Resources resources] within their [wiki:Architecture/Domains domain]. 6 21 7 === To Consoles 8 The [wiki:UserGuide/RemoteAccess/Console domain consoles] can be accessed the same way as the gateway (above), with the following differences: 9 1. Consoles can be connected to '''ONLY''' during a [wiki:GettingStarted#MakeaReservation current (and approved) reservation]. 10 1. In addition to accessing home directories and computing/running scripts, consoles can run [http://omf.orbit-lab.org OMF] commands to control [wiki:Resources resources] within their [wiki:Architecture/Domains domain] 11 1. Consoles share a [wiki:Architecture/Network#ControlPlane Control network] with [wiki:Resources resources] within their [wiki:Architecture/Domains domain] 22 === Access Resources via Console 12 23 13 === To Resources via console 14 15 * Resources can be interacted with by running commands from a Console. 16 * For example: 17 * Using [wiki:UserGuide/OmfQuickStart OMF commands] to 24 Resources can only be accessed by running commands from a console or by establishing a connection through the console. For people unfamiliar with [https://www.redhat.com/sysadmin/ssh-proxy-bastion-proxyjump ProxyJump], the following is recommended: 25 * SSH into your domain console. 26 * Use [wiki:UserGuide/OmfQuickStart OMF commands] to 18 27 * Turn resources on/off 19 28 * Load and save images 20 29 * Run OEDL Scripts with OMF exec 21 * Use SSH from a console to open an interactive session with a compute resource. 22 * Use SSH with X11 Forwarding to view a graphical window from a resource on your local machine 30 * Open an interactive session wtih SSH from a console to compute resource. 31 * Use SSH w/ X11 Forwarding to view a graphical window from a resource on your local machine. 32 * '''REMINDER''': you can only SSH w/ X11 by adding argument -X or -Y to every SSH command. 33 * Example: 34 {{{#!div style="font-size: 100%" 35 {{{#!shell 36 ssh -X USERNAME@console.DOMAIN.cosmos-lab.org 37 }}} 38 }}} 39 {{{#!div style="font-size: 100%" 40 {{{#!shell 41 ssh -X root@COMPUTE_RESOURCE 42 }}} 43 }}} 23 44 24 === To Resources directly25 This is a n advanced topic. In the event that bridging through a console adds unacceptable overhead too your use case, the following options are available:45 === Access to Resources Directly 46 This is a convenient only if bridging through the console adds unacceptable overhead or difficulty to your use case. You can only [https://www.redhat.com/sysadmin/ssh-proxy-bastion-proxyjump ProxyJump] if you have a current and approved reservation. Your resource also must be turned on beforehand. 26 47 27 * Use SSH [https://www.redhat.com/sysadmin/ssh-proxy-bastion-proxyjump ProxyJump] and similar commands to automate the connection though the console 28 * Use the [wiki:UserGuide/RemoteAccess/VPN VPN] to route arbitrary network traffic from the [wiki:Architecture/Network#ControlPlane Control Network] to or from your local machine. 48 {{{#!div style="font-size: 100%" 49 {{{#!shell 50 ssh -J USERNAME@console.DOMAIN.cosmos-lab.org root@RESOURCE 51 }}} 52 }}} 29 53 30 === Using SSH 31 The most common method of connecting to the testbed is via SSH. The SSH protocol is quite powerful, and allows interactive shell sessions, file transfer, port forwarding, and even graphical display if configured properly with other utilities. 54 * Use additional [https://man7.org/linux/man-pages/man1/ssh.1.html SSH manual/arguments] to automate the connection through the console. 32 55 33 ==== Configuring SSH Keys 34 See [wiki:UserGuide/RemoteAccess/SSH#ConfiguringSSHKeys Configuring SSH keys page]. 35 36 ==== SSH tunneling and X11 37 See [wiki:UserGuide/RemoteAccess/SshTunnel#SshTunnel SSH X11 tunneling page]. 38 39 ==== Common SSH Tips and FAQ 40 See [wiki:UserGuide/RemoteAccess/SshTips#tips SSH tips page]. 56 === Access Tips w/ SSH 57 The prominent method of connecting to the testbed is via SSH. The SSH protocol is quite powerful, allowing interactive shell sessions, file transfers, port forwarding, and even graphical displays if configured properly with other utilities. Please consult for further help: 58 * [wiki:UserGuide/RemoteAccess/SSH#ConfiguringSSHKeys Configuring SSH keys page] 59 * [wiki:UserGuide/RemoteAccess/SshTunnel#SshTunnel SSH X11 tunneling page]. 60 * [wiki:UserGuide/RemoteAccess/SshTips#tips SSH tips page]. 41 61 42 62 === Using Chrome Remote Desktop