Hi Jack,
On 08/08/14 16:32, Jack Perdue wrote:
Howdy Ken,
re: Hierarchical MNSs
I looked over the notes below. Before y'all
head home for the weekend (I may be too late), do
you happen to have any code updates for supporting
HMNSs online that I could ponder/play with?
I was planning to send out a status report on HMNS support soon given
the significant interest in this feature, and poll for experiences with
experimenting with it, but you beat me to it. ;-)
Different people have reported a couple of issues, some are yet to be
resolved.
Kilian reported a couple of issues with using an Intel toolchain (e.g.
'ictce' or 'intel') in combination with a hierarchical module naming
scheme [1].
One aspect of that is a couple of mistakes in the HierarchicalMNS, fixes
are available in framework PR#986 [2].
Another aspect is that the currently provided easyconfigs for impi and
imkl use the 'dummy' toolchain, which isn't correct in a HMNS context.
A new version of the intel toolchain that resolves this is being
contributed in easyconfigs PR#1014 [3].
In there, the problem of the GCC dependency of icc/ifort also extending
the $MODULEPATH is also being tackled (although proper support for this
in the framework will need to be added in as well, see the comment
included in the included GCC-4.8.3-libs.eb easyconfig file).
I'm not keen on changing the other ictce/intel toolchain in a similar
way, even though the change has limited impact for people already using
them in production.
It basically only results in slightly different module names for the
toolchain components, and one or two additional modules (e.g. for the
new intermediate iimpi toolchain).
Next to that, two other issues have been reported. One by Ian w.r.t. the
conflict statement in generated modules [4] (fix is pending, but pretty
straightforward), and one by Olav w.r.t. 'module load' statements for
compiler/MPI being included in module files for applications (e.g.
"module load icc" in a module for HPL) [5]. Not only is this senseless,
since you need to load the compiler and MPI before you can even see the
application modules, it's also wrong, and it causes problems when
unloading (and hence also swapping) modules.
The latter is a serious bug, that basically renders the current
HMNScsupport crippled. Up until now, it has only been discussed on the
#easybuild IRC channel and via mail (outside of the ML).
I hope to find time next week to work on the open problems, and get the
proposed fixes that are already available merged in.
Maybe I can get into getting a bugfix release out (v1.14.1), but no
promises there. In any case, these issues should get resolved by
EasyBuild v1.15.0 (early Sept'14).
If anyone is aware of other issues, please come forward.
Maybe we should also set up a conference call with the people interested
in using a hierarchical module naming scheme with EasyBuild?
Who would be interested in that?
regards,
Kenneth
[1] https://github.com/hpcugent/easybuild-framework/issues/980
[2] https://github.com/hpcugent/easybuild-framework/pull/986
[3] https://github.com/hpcugent/easybuild-easyconfigs/pull/1014
[4] https://github.com/hpcugent/easybuild-framework/issues/994
[5] https://github.com/hpcugent/easybuild-framework/issues/996
We are rolling out a new cluster and would
really like to rebuild everything using
HMNs before opening the system for production
(since changes to the module system will much
more painful afterwards). As such, I've gotten
approval to spend some time on this.
My Python kung-fu is not so great, but I'm slowly
learning more (via deploying/updating EasyBuild and
Galaxy [a bio/bio web interface]). I had some
issues with my initial test of the HMNs (which I
need to repeat since it was back when 14 first came out).
I plan on trying again this weekend, so if you
have a fork somewhere that has your latest updates,
I'd love to look it over.
Thanks,
Jack Perdue
Lead Systems Administrator
TAMU Supercomputing Facility
[email protected] http://sc.tamu.edu
SC Helpdesk: [email protected]
----- Original Message -----
From: "Kenneth Hoste" <[email protected]>
To: "EasyBuild" <[email protected]>
Sent: Tuesday, August 5, 2014 9:27:54 AM
Subject: Re: [easybuild] EasyBuild conference call: Aug 5th 2014, 3pm CET
Notes on the conf call of this afternoon are available at
https://github.com/hpcugent/easybuild/wiki/Conference-call-notes-20140805
.
On 05/08/14 09:47, Kenneth Hoste wrote:
Hello EasyBuilders,
The next EasyBuild conference call is planned for today, Aug 5th
2014,
3pm - 3.30pm (CET).
Topics that will be discussed include:
*) EasyBuild v1.15 release planning
*) improvements w.r.t. using a dummy/system toolchain
*) status update of support for hierarchical modules
Suggestions for additional topics are welcome.
Please let me know if you're planning to attend this conf call.
More information about the EasyBuild conference calls is available
at
https://github.com/hpcugent/easybuild/wiki/Conference-calls .
regards,
Kenneth
