Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Atos HPCF is not operational platform yet, and many features or elements may be gradually added as complete setup is finalised. Here is a list of the known limitations, missing features and issues.

Table of Contents

File Systems

  • There are no NetApp NFS-served filesystems yet, which means:
    • HOME is in a temporary location (Lustre). It does not come with snapshots or backup.
    • PERM is temporarily supported by an area in lustre (no backups, no snapshots), but in the future will be provided by external NFS services (see above). Please use HPCPERM in the meantime, which would offer better parallel performance  - but no snapshots or backup.
  • The select/delete policy in SCRATCH has not been enforced yet.

Missing Features

Comprehensive software stack

...

Alternatively, you may use sacct to get some of the statistics from SLURM once the job has finished.

Connectivity

  • Direct access to the Atos HPCF through ECACCESS or Teleport is not yet available. See HPC2020: How to connect for more information.
  • SSH connections to/from VMs in Reading running ecFlow servers are not available. For more details on ecFlow usage, see HPC2020: Using ecFlow.
  • Load balancing between Atos HPCF interactive login nodes is not ready yet. When implemented, an ssh connection into the main alias for the HPCF may create a session in an arbitrary login node.

Filesystems

PERM is temporarily supported by Lustre (no backups, no snapshots), but in the future will be provided by external NFS services. Once ready, the contents would be migrated without the user intervention.

The select/delete policy in SCRATCH has not been enforced yet.

See HPC2020: Filesystems for all the details.

Known issues

Intel MKL > 19.0.5 performance issues on AMD chips

...