You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I didn't found documentation on how it was intended to use Spack inside OHPC.
The spack-ohpc pakage leaves Spack at the /opt/ohpc/admin directory.
It has a module that it's only accessed by root
All spack compiled packages and corresponding modules stay inside the /opt/ohpc/admin/spack dir.
So cluster users have no easy way to access those packages and modules.
And default NFS export don't even allows to access those packages from the compute nodes.
Didn't make much sense to me if users and nodes cannot access it.
I guess that the basic usage should be that only cluster admins have access to compile packages and create modules using that installation of spack, and cluster users are allowed to use those packages by loading the modules. This way cluster admins can decide which packages to support and they should be the ones with enough knowledge to understand what options to choose and how to compile packages for the cluster.
So in order to do that I had to make some changes.
Allow users to access spack created modules:
By changing /etc/profile.d/lmod.sh both in frontend and nodes and adding /opt/ohpc/admin/spack/0.21.2/share/spack/modules/linux-rocky9-sandybridge/
to the cluster users MODULEPATH variable
Allow compute nodes to access compiled packages and modules:
By adding spack directory to /etc/exports: /opt/ohpc/admin/spack *(ro,no_subtree_check,fsid=12)
And mounting that export in the nodes adding the following line to /etc/fstab of the nodes: frontend.ip.address:/opt/ohpc/admin/spack /opt/ohpc/admin/spack nfs nfsvers=3,nodev 0 0
Perhaps there is need to decide what could be the default way to use it in ohpc and add something on the documentation?
Thanks!
The text was updated successfully, but these errors were encountered:
I didn't found documentation on how it was intended to use Spack inside OHPC.
/opt/ohpc/admin
directory./opt/ohpc/admin/spack
dir.Didn't make much sense to me if users and nodes cannot access it.
I guess that the basic usage should be that only cluster admins have access to compile packages and create modules using that installation of spack, and cluster users are allowed to use those packages by loading the modules. This way cluster admins can decide which packages to support and they should be the ones with enough knowledge to understand what options to choose and how to compile packages for the cluster.
So in order to do that I had to make some changes.
Allow users to access spack created modules:
By changing
/etc/profile.d/lmod.sh
both in frontend and nodes and adding/opt/ohpc/admin/spack/0.21.2/share/spack/modules/linux-rocky9-sandybridge/
to the cluster users
MODULEPATH
variableAllow compute nodes to access compiled packages and modules:
By adding spack directory to
/etc/exports
:/opt/ohpc/admin/spack *(ro,no_subtree_check,fsid=12)
And mounting that export in the nodes adding the following line to
/etc/fstab
of the nodes:frontend.ip.address:/opt/ohpc/admin/spack /opt/ohpc/admin/spack nfs nfsvers=3,nodev 0 0
Perhaps there is need to decide what could be the default way to use it in ohpc and add something on the documentation?
Thanks!
The text was updated successfully, but these errors were encountered: