Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 12 additions & 6 deletions _episodes/01.7-InteractiveComputingResources.md
Original file line number Diff line number Diff line change
Expand Up @@ -19,11 +19,11 @@ Fermilab provides DUNE with 18 virtual machines that are accessible to any DUNE

### 16 General Purpose Virtual Machines - gpvms

There are 16 `dunegpvm01-dunegpvm16` for everyday use which have 12 GB of memory and 4 CPU's. These are for developing and testing code, for submitting batch jobs and for running small analysis jobs.
There are 16 `dunegpvm01-dunegpvm16` for everyday use which have 12 GB of memory and 4 CPU's. These are for developing and testing code, for submitting batch jobs and for running small analysis jobs. Note that the number of gpvms is likely to decrease in the future as we move to a smaller number of more powerful gpvms.

The default OS on the gpvms is Alma 9, if you need SL7, use the Apptainers described in [SL7 setup]({{ site.baseurl }}/sl7_setup).
The default OS on the gpvms is Alma 9; if you need SL7, use the Apptainers described in [SL7 setup]({{ site.baseurl }}/sl7_setup).

They have access to your home area, `/cvmfs/` and the `/exp/dune/data`, `/exp/dune/app` and `/pnfs/dune`. There is also a small `/tmp` area.
They have access to your home area (/nashome/firstletterofusername/username), `/cvmfs/` and the `/exp/dune/data`, `/exp/dune/app` and `/pnfs/dune`. There is also a small `/tmp` area.

Some resources (such as batch systems and `/pnfs/`) require "tokens" to access. See the [tokens]({{ site.baseurl }}/Tokens) page for more information.

Expand Down Expand Up @@ -54,16 +54,22 @@ Users with CERN credentials can also use `lxplus`. See [lxplus.cern.ch](https:/

## Remote connections

People wishing to use remote connections via VSCode or tunnels are strongly encouraged to follow the instruction in the DUNE wiki linked below.
People wishing to use remote connections via VSCode or tunnels for virtual desktops shall follow the instruction in the DUNE wiki linked below.

[Using tigervnc to get X running on a gpvm](https://wiki.dunescience.org/wiki/DUNE_Computing/Using_VNC_Connections_on_the_dunegpvms)

[Using VSCode on a gpvm without running all your extensions](https://wiki.dunescience.org/wiki/DUNE_Computing/VSCode_and_Claude_on_the_GPVMs)

Please do not use other VNC clients that set up a full desktop manager (e.g. Ubuntu/gnome WM, etc ) and only use lightweight VNCs. There are limited resources on the GPVMs. We don't need N instances of your calendar app running on our development machines. Especially as they tend to stay around for weeks.
Do not use other VNC clients that set up a full desktop manager (e.g. Ubuntu/gnome WM, etc ) and only use lightweight VNCs. There are limited resources on the GPVMs. We don't need N instances of your calendar app running on our development machines. Especially as they tend to stay around for weeks, and in some cases, have been observed to consume over 2 GB of memory!

It is also important to disable a number of the background processes related to virtual desktops. There are detailed instructions on the DUNE Wiki:

[Disabling GNOME-related background services (these can turn on even if using IceWM unless they are disabled)](https://wiki.dunescience.org/wiki/DUNE_Computing/Using_VNC_Connections_on_the_dunegpvms#Disabling_some_gnome-related_services)

## Be mindful of computer security

Most of our standard physics code is vetted and tested and is available from `cvmfs` on all of these machines. Be very cautious about downloading and installing untested packages from the internet. Major software sources such as PyPI and conda-forge monitor for malicious code but can't stop everything. And even legit software can have unexpected resource needs that may not be workable on our systems.

Installation of rogue software can result in you, or worse, the collaboration losing computing privileges.
Installation of rogue software can result in you, or worse, the collaboration losing computing privileges.

As a reminder, the Fermilab Policy on Computing Can be Found [here](https://fermi.servicenowservices.com/kb_view.do?sysparm_article=KB0013868). The CERN computing rules are [here](https://security.web.cern.ch/rules/en/index.shtml).
Loading