JupyterHub¶
JupyterHub is the primary interactive interface to FLAME. It gives you a full JupyterLab notebook environment, including a terminal, running on the cluster with access to GPUs, all from your web browser without you installing any additional software.
Accessing FLAME via JupyterHub¶
Like all FLAME services, JupyterHub delegates authentication to Drexel Connect, via Globus Auth (See Authentication for details).
To access Jupyter Hub:
- Go to https://jupyter.flamecluster.io in your web browser
- Click "Sign in with Globus"
- You will be redirected to a Globus Auth login screen. Choose "Drexel University" as your institution
- You will be redirected to Drexel Connect. Sign in as normal using your Drexel username and password
- You will be redirected back to JupyterHub, logged in
Launching a notebook server¶
After logging in, you will see a configuration form where you can select your workspace namespace and set your resource requests (CPU, memory, and optionally a GPU type and count). When you're ready, click Start and JupyterHub will launch your session.
Tip
Choose the smallest resource size that fits your task. This helps keep resources available for others and generally means faster startup times.
Sessions are automatically stopped after 24 hours of inactivity. You can also stop your server manually from the JupyterHub control panel when you're done.
Your files¶
Notebooks come with two storage locations that persist across sessions:
/home/ubuntu: your personal home directory. For your own code, configuration files, etc./workspace-- shared storage for all workspace members. For shared data, code, docs, and configuration.
For more details, see Storage.
Connecting with VSCode¶
If you prefer using the Visual Studio Code rather than a web browser, you can connect a local VSCode window to your running notebook. This lets you use the VSCode for file browsing, editing, transfer and terminal, just like you would on your own machine or with an SSH remote connection.
For details, see VSCode.