HPC2020: Local SSD storage for interactive sessions

When using standard, non-gpu ecinteractive or JupyterHub sessions, you can enjoy some fast, local SSD storage that can be persisted across sessions in addition to the usual filesystems available. Made available as $LOCALSSD, its contents are automatically archived into your $HPCPERM when your interactive session finishes so you can recover them on your next session and continue where you left off. This feature is primarily aimed to speed up development workflows where builds are required.

How does it work?

Before starting your standard, non-gpu interactive session, make sure you request the amount of local disk space you are going to require. 

• With ecinteractive using the -s option. For example, to request 30 GB:
  

  ecinteractive -s 30

• With JupyterHub, select the desired value from the "Temporary Storage" dropdown, which is available on the "ECMWF Atos HPC" or "ECMWF Atos ECS" profiles.

When your session starts, you will have a space in the local disk pointed to by $LOCALSSD environment variable that you can use in your session

At the end of the session, either by your choice killing the session or wall time, the contents of $LOCALSSD will be archived automatically into a special directory in your $HPCPERM under:

$HPCPERM/.DO_NOT_DELETE_LOCALSSD_ARCHIVE/

Note that logging out of the session does not terminate it, so no archival happens at that point as you can reconnect to it later while it remains active.

How do I restore my LOCALSSD contents?

There is no automatic restore of your LOCALSSD contents, so next time you open a new interactive session, you will be able to restore the contents of the local storage from your previous one running the following command:

ec_restore_local_ssd

How much LOCALSSD space can I use?

You must request how much space you need when you start your interactive session as described above. You will not be able to exceed that limit while in that interactive session.