[Swift-devel] Fwd: [pads-users] Switching for SoftEnv to Modules

[Michael Wilde]

This would be a good time to ensure that we have up to date Swift modules and softenv packages installed on all CI and Argonne machines:

- CI login hosts and Swift lab systems (bridled, communicado)
- PADS
- Beagle

- MCS login hosts and compute servers
- Fusion
- Intrepid, Surveyor, Challenger, Eureka, Gadzooks

Mike


----- Forwarded Message -----
From: "Forum for PADS user discussions" <pads-users at ci.uchicago.edu>
To: pads-users at ci.uchicago.edu
Sent: Friday, January 6, 2012 10:26:03 AM
Subject: [pads-users] Switching for SoftEnv to Modules

Because Beagle requires the use of Modules and because FutureGrid (of which CI runs a testbed) and TeraGrid XD have settled on using Modules, we thought it would be beneficial for all the software management environments to be consistent. So we've decided to migrate PADS, and the rest of the CI, away from SoftEnv to Modules. 

We'll be doing the migration in stages. The first stage will be to make SoftEnv use the same installations as Modules. This will help us identify software packages that still need to be installed the Modules way as well as test out the software that's currently there. During this time we highly encourage users to try out and test Modules as much as possible. We're shooting to have this phase done within 2 weeks.

The second stage will be to remove all the extraneous SoftEnv software installations to clean up the software tree and flush out any remaining un-migrated software. We're shooting to have this phase done by the February maintenance day.

The third stage will be to turn off SoftEnv and make Modules the default on PADS. We're shooting for this to be done by the March maintenance day to ensure everyone has adequate time to fully test the software tree.

I've been using Modules exclusively for some months and several other users have been using it for several weeks, so I feel confident the basics are all there and working. If you'd like to start using Modules now and get a jump start, you can do the following:

1) comment out everything in your ~/.soft file. Don't remove the file, just comment everything out.
2a) For bash/zsh users add the following to your ~/.bashrc or ~/.zshrc, respectively:
. /soft/Modules/etc/modules.sh

2b) For csh/tcsh users add the following your ~/.cshrc or ~/.tcshrc, respectively:
source /soft/Modules/etc/modules.csh

That's it! I'll be working on Modules documentation over the next month, but here are some basic commands:

- module list: Show all currently loaded modules in your environment
- module avail: Show all available modules for use
- module load <module>: Load the specified module (and any dependencies) into your environment
- module unload <module>: Unload the specified module from your environment
- module purge: Reset your environment to a pristine setting
- module show <module>: Show what environment variables the specified module sets

You can also create a ~/.modulerc file so that certain modules will get loaded at initialization - useful for having modules loaded for submitted jobs:

#%Module1.0

module load openmpi
module load hdf5

#EOF

As always if you have any questions or concerns, please email pads-support at ci.uchicago.edu.




_______________________________________________
pads-users mailing list
pads-users at ci.uchicago.edu
https://lists.ci.uchicago.edu/cgi-bin/mailman/listinfo/pads-users

-- 
Michael Wilde
Computation Institute, University of Chicago
Mathematics and Computer Science Division
Argonne National Laboratory