> From: "Fotis Georgatos" <[email protected]> > Sent: Tuesday, June 3, 2014 5:05:10 PM
> On Jun 3, 2014, at 9:13 PM, Jack Perdue wrote: > > jack (learning EB in order to facilitate software > > deployment on TAMU's new clusters) > > Talking about TAMU, here's a moment to ask about some other tricky > bisiness, ref.: > https://github.com/hpcugent/easybuild/wiki/Wishlist#modules-namespace-from-various-hpc-sites > (fyi. this was an August 2012 wishlist - many things implemented > already - congrats ;-) > > Jack, do you have as requirement the nested module namespace > "netcdf/4.1.1/pgi/10.3/64" or, > you plan to get away with it, by switching to Lmod-type hierarchical > schemes instead? > Basically, I wonder if you plan to develop custom-naming-schemes for > module namespace, > which is going to be an interesting experiment, one way or another, > in your case. > The challenging piece is, where "64bits" and such name variations end > up living. We will most definitely be using Lmod on the new clusters. I am currently using the old TCL modules for now while I play with EB on our old cluster, but I've been exploring how we plan to use Lmod and EB on the new ones (x86_64/P7/BGQ). In fact, I was hoping to "corral" Robert at TACC next Friday if he was around to possibly discuss some of the questions/approaches we were pondering. Partly because we really need to talk to him at some point and partly because the Texas Linux Festival will be going on in Austin on Saturday and I figured it was a good excuse to head down a day early. :) Alas, I see from this thread that he won't be there (he pretty much told me as such earlier this summer but plans change... oh well... any TACC EasyBuilders want some visitors next Friday? ;). I/we haven't really nailed down the module hierarchy yet. I like Lmod's Core/Compiler/MPI/etc. chain, but see issues there. I haven't really looked at the possibilities with EB's different module hierarchies yet. For now, in terms of architecture, we are looking at a shared (GPFS) filesystem with something like: /software/x86_64 /software/p7 /software/bgq with maybe some magic so our users only see the "/software" that is appropriate for the cluster they are on. Anyway... thanks everyone for the responses. This gives me something to move forward with. I'll have to learn how to use our new github.tamu.edu (being introduced here tomorrow). First on my list will be EB (I've got a lot of new easyconfigs and other changes that aren't upstream). jack
