Track availability / installation of Intel oneAPI (LLVM) compilers on tier1 hosts

[rickgrubin-noaa]

Is your feature request related to a problem? Please describe.

Track the availability, and if necessary, spack-stack installation, of Intel oneAPI (LLVM) compilers on tier1 hosts.

Describe the solution you'd like

Note: require [email protected] or later because of current support of, and bugs in, previous releases.

Current status of each tier1 host is listed below, per release/1.8.0 configs/sites/tier1/<host>/compilers.yaml or if host is marked with an asterisk (*), verified via module available on the host itself. This is also shown below for each host.

NB:

• do not have access to all tier1 hosts, please update the list if able.

Hosts

• acorn
  • [email protected] (per configs/sites/tier1/acorn/compilers.yaml)
• atlantis
  • [email protected] (per configs/sites/tier1/atlantis/compilers.yaml)
• derecho *
  • 2024.2.1 (via module available)
• discover
  • scu-16
    • [email protected] (per configs/sites/tier1/discover-scu16/compilers.yaml)
  • scu-17
    • [email protected] (per configs/sites/tier1/discover-scu17/compilers.yaml)
• gaea *
  • c5 *
    • [email protected]
    • installed via spack-stack
    • module use module use /ncrc/proj/epic/spack-stack/modulefiles
    • module load intel-oneapi-compilers/2024.2.1
  • c6 *
    • [email protected]
    • installed via spack-stack
    • module use module use /ncrc/proj/epic/spack-stack/c6/modulefiles
    • module load intel-oneapi-compilers/2024.2.1

Via email from GFDL 21-October-2-24:

Update:
Currently, the CPE does not yet support 2024.2 -- we are waiting on word from ORNL on when this compiler will be supported.

For now, users can still use 2024.2 on c5/c6 at their own risk. cc and CC wrappers are not expected to work.

In addition, intel packages are not managed in a sensical manner. When there is an update to Intel 2024.2 release (i.e. from 2024.2.0 -> 2024.2.1 ) they put everything into the 2024.2 package repo location instead of making a separate release for 2024.2.1. ORNL does not have much control if what will be available in the 2024.2 module will be exactly what the user had wanted from the specific 2024.2.1 release, nor can they specifically install 2024.2.1 version because Intel doesn't do version and releases properly.

• hera *

  • [email protected] (via module available)

• hercules *

  • [email protected]
  • installed via spack-stack
  • module use /work/noaa/epic/role-epic/spack-stack/hercules/modulefiles
  • `module load intel-oneapi-compilers/2024.2.1

• jet *

  • [email protected] (viamodule available)

• narwhal

  • [email protected] (per configs/sites/tier1/narwhal/compilers.yaml)

• nautilus

  • [email protected] (per configs/sites/tier1/nautilus/compilers.yaml and issue #912)

• orion

  • [email protected]
  • installed via spack-stack
  • module use /work/noaa/epic/role-epic/spack-stack/orion/modulefiles
  • module load intel-oneapi-compilers/2024.2.1

• s4

  • [email protected] (per configs/sites/tier1/s4/compilers.yaml)

• sandy

  • GNU only: [email protected] (per configs/sites/tier1/sandy/compilers.yaml)

• CSP

  • noaa-aws *
    • [email protected]
  • noaa-azure *
    • [email protected]
  • noaa-gcloud *
    • [email protected]

• ursa

  • [email protected] (viamodule available)
    • see also Add new machine: NOAA Ursa (Hera's follow-on)

Additional context

Requests to upgrade to the latest supported version of oneAPI compilers (see link below) have been made on all NOAA tier1 hosts.

Intel® Toolkits, AI Tools, Compilers Supported Product Versions

[rickgrubin-tomorrow]

Regarding progress on hera, see: Install spack-stack 1.8.0 (and all add-on envs needed for UFS WM @ develop) with LLVM compilers on Hera #1345