Hi Jordi,
On 09/03/2017 09:01, Jordi Blasco wrote:
Good morning,
In general, each MPI implementation require some additional
configuration options in order to enable full support for a particular
workload manager.
In addition to that, some MPI versions also require additional
environment variables or even different syntax/options in the
configuration options.
For a regular HPC center is easy to tweak the MPI easybuild config in
order to meet the system requirements. Unfortunately, this is a
significant overhead when you have to maintain several clusters using
different workload managers and MPI implementations/versions (we are a
HPC consulting company).
We would like to implement a logic in the MPI easyblocks based on data
gathered from the system (i.e. workload manager config file) or from
the easybuild configuration.
This logic could be also used in the easyblocks of some applications
like GAMESS, ANSYS Fluent/CFX, Abaqus or FSL which requires some
patches in order to work properly with some workload managers.
This could turn the current MPI easyconfig files into workload manager
agnostic. Also, it could save a lot of time for people with short
exposure in HPC or in some particular workload manager.
We know what to do at the easyblock level, but we would like to
receive developers feedback before to invest time and efforts in the
EasyBuild framework.
Can you please provide some directions and/or suggestions in this regard?
This sounds like a good idea...
In my view, this would involve supporting a way to configure EasyBuild
for your particular workload manager, and expose a couple of functions
that can be leveraged in easyblocks to query for the necessary workload
manager information.
Can you elaborate a bit on what you have in mind now exactly?
What kind of information would need to be provided to the EasyBuild
framework, what kind of information do you need in easyblocks?
Maybe we should implement some kind of auto-detect mechanism in
framework, where the necessary information is collected automatically
based on which workload manager is used (so, you would only need to
configure EasyBuild with --use-resource-manager=Torque for example), but
also provide a way to override those values in case the auto-detection
gets them wrong?
regards,
Kenneth
Thanks!
Kind regards,
Jordi
--
------------------------------------------------
Jordi Blasco • Co-founder
[email protected] <mailto:[email protected]>
Tel. +34 639 292676 <tel:%2B34%20639%20292676>
www.hpcnow.com <http://www.hpcnow.com/>
Follow us onTwitter <http://goo.gl/HpgUE>•Linkedin <http://goo.gl/kgC9c>
------------------------------------------------
