-
-
Notifications
You must be signed in to change notification settings - Fork 3
Description
There are some notes that Rucio authentication isn't working on AL9, but it seems to be fine as long as I comment out the "export RUCIO_ACCOUNT=justinreadonly" line in the setup script. Is this because we're getting tokens from justin on SL7 but using htgettoken on AL9, so the justinreadonly account isn't recognized? Might be good to clarify what's going on here.
In the storage spaces section, the pnfs2xrootd command is introduced before the code block to setup dunesw which gives you that command. Also, the example file for that was on tape so when I tried to open in in root I got stuck waiting for it to stage. Its online again now since I accessed it, probably we just need to go through and make sure any example files are online the day before the tutorial.
The gfal-xattr command doesn't seem to work quite right on the Fermilab tape files. Online files are reported correctly, but files that should be "NEARLINE" instead come back as "UNKNOWN". As far as I can tell it works as expected for other RSEs, so in my merging script I just put in a special case override for "UNKNOWN" files at FNAL.
In the CVMFS section, maybe it would be good to mention how to add files to CVMFS? Like the justin-cvmfs-upload command, that might be explained in the other batch computing training though.
In the Spack section, I think the purpose of the "spack env activate dune-tutorial" command is unclear. We don't start an environment in the older Spack setup, is it just a way to easily install standard versions of all the software instead of loading each one individually? The name seems to imply this is just an environment for people to mess with during the tutorial, do we expect them to keep using it afterward or to switch to something else?