tutorials_interactivegpu

Differences

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

Link to this comparison view

Next revision		 Previous revision
tutorials_interactivegpu [2026/05/29 14:03] – created docuadmintutorials_interactivegpu [2026/05/29 15:02] (current) – [Ending the Session] docuadmin
Line 1: Line 1:
-# Quick Start Guide: Launching an Interactive Desktop on an HPC Cluster with Open OnDemand +===== Launch an Interactive Desktop on the GPU Node =====
- +
-## What is Open OnDemand?+
  
 Open OnDemand is a web-based interface that provides access to HPC cluster resources through a browser. It allows you to launch interactive desktop sessions, run applications, manage files, and submit jobs without using the command line. Open OnDemand is a web-based interface that provides access to HPC cluster resources through a browser. It allows you to launch interactive desktop sessions, run applications, manage files, and submit jobs without using the command line.
 +Through Open OnDemand users can run an interactive desktop session on the GPU node of HPC2.
  
----+==== Access the pre-configured session ==== 
 +  * Log in at [[https://hpc2.grinnell.edu]] using your Grinnell College credentials. 
 +  * Click the GPU Desktop tile under the //*Interactive Apps//* heading.
  
-# Launching an Interactive Desktop Session+{{ :interactivegpu1.png?nolink&400 |}}
  
-## 1. Log In+==== Configure the Job and Launch Session ====
  
-Open your cluster’s Open OnDemand URL in a web browser and sign in with your HPC credentials.+You will be presented with a job submission form. Since this interactive job is already configured, you'll only need to specify the amount of time (in hours) you expect the job to run. Click 'Launch' to submit the job to the scheduler. Your job will be placed in the queue.
  
-Typical login page methods include: +{{ :interactivegpu2.png?nolink&400 |}}
-- Institution SSO +
-- Username/password +
-- Multi-factor authentication+
  
----+==== Wait for the Job to Start ====
  
-## 2. Open the Interactive Apps Menu+You'll be directed to a page displaying your active and recent sessions. Your new session status will typically show: 
 +  * Queued 
 +  * Starting 
 +  * Running
  
-After logging in:+{{ :interactivegpu3.png?nolink&400 |}}
  
-1. Locate the **Interactive Apps** menu at the top of the page. +Once the job starts, a button titled //*Launch GPU Desktop//* will appear. Click it to open the remote desktop in your browser.
-2. Select the desired desktop environment, such as: +
-   - Interactive Desktop +
-   - Remote Desktop +
-   - XFCE Desktop +
-   - GNOME Desktop+
  
-(The exact names vary by cluster.)+{{ :interactivegpu4.png?nolink&400 |}}
  
----+==== Use the Desktop Environment ====
  
-## 3. Configure the Job+Inside the desktop session, you can: 
 +* Open terminals 
 +* Run GUI applications 
 +* Use IDEs
  
-You will be presented with a job submission form. +{{ :interactivegpu5.png?nolink&400 |}}
- +
-Typical options include: +
- +
-| Setting | Description | +
-|---|---| +
-| Account / Project | Billing or allocation account | +
-| Partition / Queue | Cluster queue to run on | +
-| Number of Cores | CPU cores requested | +
-| Memory | RAM allocation | +
-| Wall Time | Maximum session duration | +
-| GPU Options | Optional GPU resources | +
-| Desktop Environment | XFCE, GNOME, etc. | +
- +
-Choose resources appropriate for your workload. +
- +
-Example: +
-- 4 CPU cores +
-- 8 GB RAM +
-- 2-hour wall time +
- +
---- +
- +
-## 4. Launch the Session +
- +
-Click: +
- +
-- **Launch** +
-- **Submit** +
-- or **Start** +
- +
-depending on your site configuration. +
- +
-The job will enter the scheduler queue. +
- +
---- +
- +
-## 5. Wait for the Job to Start +
- +
-Your session status will typically show: +
-- Queued +
-- Starting +
-- Running +
- +
-Once the job starts, a button such as **Launch Desktop** or **Connect to Desktop** will appear. +
- +
-Click it to open the remote desktop in your browser. +
- +
---- +
- +
-## 6. Use the Desktop Environment +
- +
-Inside the desktop session, you can: +
-- Open terminals +
-- Run GUI applications +
-- Use IDEs +
-- Visualize data +
-- Launch MATLAB, RStudio, ParaView, etc.+
  
 The session behaves similarly to a Linux desktop computer running on the cluster. The session behaves similarly to a Linux desktop computer running on the cluster.
  
----+{{ :interactivegpu6.png?nolink&400 |}}
  
-# File Access+===== File Access =====
  
 You can transfer and manage files using: You can transfer and manage files using:
-- The **Files** menu in Open OnDemand +* The //*Files//* menu in Open OnDemand 
-- SCP/SFTP +* SCP/SFTP
-- Shared storage mounted on the cluster+
  
-Your home directory and project storage are typically available automatically.+Your home directory on the cluster is available in the desktop session.
  
---- +===== Ending the Session =====
- +
-# Ending the Session+
  
 When finished: When finished:
  
-1. Save your work. +  * Save your work. 
-2. Close applications. +  * Close applications. 
-3. Return to the Open OnDemand dashboard. +  * Return to the Open OnDemand dashboard. 
-4. Select **My Interactive Sessions**. +  * Select //*My Interactive Sessions//*. 
-5. Click **Delete** or **Terminate** to end the job.+  * Click //*Delete//* to end the job.
  
 Closing the browser tab alone may not stop the job. Closing the browser tab alone may not stop the job.
  
----+===== Troubleshooting =====
  
-# Troubleshooting+==== Job Stays Queued ====
  
-## Job Stays Queued+The cluster is likely busy and is already using the GPUs for other running sessions. You can see what jobs are currently running by accessing the //*Jobs//* menu in Open OnDemand and selecting 'All Jobs'.
  
-Possible causes: +==== Desktop Will Not Open ====
-- Cluster is busy +
-- Requested resources are too large +
-- Incorrect account or partition +
- +
-Try reducing: +
-- CPU count +
-- Memory +
-- Wall time +
- +
---- +
- +
-## Desktop Will Not Open+
  
 Possible causes: Possible causes:
-- Browser popup blocker +  * Browser popup blocker 
-- Expired session +  * Expired session 
-- VNC/websocket startup failure+  * VNC/websocket startup failure
  
 Try: Try:
-- Refreshing the page +  * Refreshing the page 
-- Relaunching the job +  * Relaunching the job 
-- Using a different browser+  * Using a different browser
  
---- +==== Session Disconnects ====
- +
-## Session Disconnects+
  
 Interactive jobs automatically terminate when: Interactive jobs automatically terminate when:
-- Wall time expires +  * Wall time expires 
-- The job is canceled +  * The job is canceled 
-- Cluster maintenance occurs+  * Cluster maintenance occurs
  
 Save work frequently. Save work frequently.
  
---- +===== Best Practices =====
- +
-# Best Practices+
  
-- Request only the resources you need. +* Request only the resources you need. 
-- Use shorter wall times when possible. +* Use shorter wall times when possible. 
-- Terminate unused sessions promptly. +* Terminate unused sessions promptly. 
-- Use interactive desktops for visualization and development, not large batch production runs.+* Use interactive desktops for visualization and development, not large batch production runs.