With the introduction of arm on AWS it seems sensible to have a shot at supporting CentOS arm clusters.
So far, a base CentOS arm AMI has been created in our account and flight-runway, flight-starter, flight-env and flight-desktop RPMs have been built for this architecture. While the RPMs do build and install without issue, there are some problems that come up during testing and general usage.
Supported Envs
It may be the case that certain software environments do not have arm support and therefore should be hidden/tagged as being incompatible instead of showing up in flight env avail.
A breakdown of the envs and arm support are below.
Env
Installs on arm?
Can install software?
Notes
Conda
n
n
Easybuild
y
y
Successfully compiled perl
Gridware
y
y
Successfully compiled memtester
Modules
y
n/a
Installs without issue so placing modules in place should work
Singularity
n
n
Potentially supported for a from-scratch build, issues executing go binary as it is x86
Spack
y
y
Actions
Hide non-supported arm software envs
Further test "supported" envs to ensure that any limitations are known
Background
With the introduction of arm on AWS it seems sensible to have a shot at supporting CentOS arm clusters.
So far, a base CentOS arm AMI has been created in our account and flight-runway, flight-starter, flight-env and flight-desktop RPMs have been built for this architecture. While the RPMs do build and install without issue, there are some problems that come up during testing and general usage.
Supported Envs
It may be the case that certain software environments do not have arm support and therefore should be hidden/tagged as being incompatible instead of showing up in
flight env avail.A breakdown of the envs and arm support are below.
gobinary as it is x86Actions