Changes for the information available through the squeue command

All,

We are currently in a phase of compliance with the constraints related
to the GDPR; this limits in particular the access to the slurm database.
The tool squeue is impacted with this limitation. Users only see
information about their jobs when making queries (this is also the case
for all other slurm commands, scontrol, sacct...).

The sinfo command can still be used to get an overview of the platform
usage. The state of the nodes and a filtered output of the squeue
command are available on the platform web page
https://www.plafrim.fr/jobs-monitoring/

This page is currently being updated to report as much information as
possible to the users. We will keep working on it in the coming days and
weeks, to hopefully meet everyone's expectations.

Please note this address is only available once signed in on the web
site (you need to use the WP identifiers obtained at the account creation).

Cheers,

The PlaFRIM team

PlaFRIM discussion team on mattermost

Dear all,

A PlaFRIM discussion team is now available on the Inria mattermost
server. PlaFRIM users got an an email with the link to join.

This team is intended for discussions on any subject related to the use
of the platform. Channels can be created for some specific needs. In any
cases, here some rules to follow

- DO NOT USE any channel to report tickets, sending an email to the
technical team plafrim-support AT inria.fr is the only way to submit tickets.

- Refrain from having NON-SERIOUS conversations or trolls.

For those not having Inria email addresses, an external account must be
created for you to access the mattermost server. Please send an email
back to nathalie.furmento AT labri.fr if you need such an account.

Cheers,

The PlaFRIM technical team

New parallel storage space

A new parallel BeeGFS file system (see https://www.beegfs.io/content/) is now available on PlaFRIM. You will find a /beegfs/<LOGIN> directory on all PlaFRIM nodes.
This parallel file system replaces the /lustre storage which is no longer under warranty and is not recommended.

The data in this directory are not saved. The quota is 1 TB per user.
If you need to write/read massively and/or in parallel, this is the preferred file system unlike your /home/<LOGIN> directory.

Information on all available storage spaces can be found in the plafrim website’s FAQ (see here).

Please do not hesitate to contact us if you need further information

New PlaFRIM nodes fingerprint

Many of you are reporting connection problems related to changing the fingerprint of development servers when connecting to SSH.

To make sure you can accept this change, you will find below the new fingerprint of these servers :

SHA256:HTzNYIkxeVcDVORkoKXleJTOEqbtq5gs9UfqjyHBOGY

Do not hesitate if you need more information.

Migration

As indicated in the message of November 8th, the migration is ongoing.

Currently, as a reminder:

   1.  when you connect to PlaFRIM, you arrive on the devel01 or devel02 front nodes, which are latest generation Skylake machines.
   2.  you can still connect to the old front node by typing ‘ssh plafrim2’; this part of the platform (miriel, breeze, mouse, arm01, sirocco…) will be migrated quickly to the new version of the platform
   3. quickly, you will find on PlaFRIM:
        * the machines you have been working on until now
        * the new bora machines (dual-socket Skylake 36 cores and 192 GB of memory)
        * modules with default modules dedicated to the target architecture you are working on
        * a /dev space for modules where all users can provide their own software stacks available to other users; it will be necessary to redo all previous dev modules, the old ones being no longer functional for this new version of the platform
        * a single slurm partition (routing) that allows you to address all machines; to choose a particular category of machines, you can specify the associated “feature” (to know the “features” associated with a node: sinfo -Nel) using the -C option of slurm (salloc -C Bora, for example)
        * guix to manage your experimental environments

Finally, if at the first connection on this new platform you have a message containing:    > ssh-keygen -f “~/.ssh/known_hosts” -R “plafrim-ext”
type the given command and everything should work