Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

spack usage #1995

Closed
gustavoberman opened this issue Jul 9, 2024 · 4 comments
Closed

spack usage #1995

gustavoberman opened this issue Jul 9, 2024 · 4 comments

Comments

@gustavoberman
Copy link

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!

@adrianreber
Copy link
Member

Thanks for the detailed description. We will discuss this in the technical steering committee and see if we can make it easier to use spack.

@adrianreber adrianreber added the tsc label Aug 8, 2024
Copy link

github-actions bot commented Sep 8, 2024

A friendly reminder that this issue had no activity for 30 days.

@adrianreber adrianreber added this to the 3.2 milestone Sep 8, 2024
@adrianreber
Copy link
Member

After discussing it in the TSC we will look into making spack available also to non-root users.

@adrianreber
Copy link
Member

Should be fixed in 3.2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants