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 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 if you need such an account.


The PlaFRIM technical team

New parallel storage space

A new parallel BeeGFS file system (see 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 :


Do not hesitate if you need more information.


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

PlaFRIM evolutions and calendar

We remind you that from next Tuesday, disruptions are to be expected on PlaFRIM.
When you connect to PlaFRIM, you will be connected to the new nodes available (devel01 and devel02). You will then be able to submit jobs on the new bora001 to bora040 nodes.
As long as PlaFRIM2 nodes are not migrated to PlaFRIM3, you can still connect to the old development nodes (devel11 to devel13) via the “ssh plafrim2” command from the new devel nodes (devel01 or devel02).
The planned schedule remains the same, migrate as many nodes as possible to PlaFRIM3 over the next week.
We still have some configurations to make so that everything is fully operational on PlaFRIM3. Feel free to test it next Tuesday and give us feedback via

Feel free to contact us for any information you may need about this migration.