Open MPI logo

Open MPI Development Mailing List Archives

  |   Home   |   Support   |   FAQ   |   all Development mailing list

Subject: Re: [OMPI devel] RFC: Force Slurm to use PMI-1 unless PMI-2 is specifically requested
From: Christopher Samuel (samuel_at_[hidden])
Date: 2014-05-07 21:15:06

Hash: SHA1

Hi all,

Apologies for having dropped out of the thread, night intervened here. ;-)

On 08/05/14 00:45, Ralph Castain wrote:

> Okay, then we'll just have to develop a workaround for all those
> Slurm releases where PMI-2 is borked :-(

Do you know what these releases are? Are we talking 2.6.x or 14.03?
The 14.03 series has had a fair few rapid point releases and doesn't
appear to be anywhere as near as stable as 2.6 was when it came out. :-(

> FWIW: I think people misunderstood my statement. I specifically
> did *not* propose to *lose* PMI-2 support. I suggested that we
> change it to "on-by-request" instead of the current "on-by-default"
> so we wouldn't keep getting asked about PMI-2 bugs in Slurm. Once
> the Slurm implementation stabilized, then we could reverse that
> policy.
> However, given that both you and Chris appear to prefer to keep it
> "on-by-default", we'll see if we can find a way to detect that
> PMI-2 is broken and then fall back to PMI-1.

My intention was to provide the data that led us to want PMI2, but if
configure had an option to enable PMI2 by default so that only those
who requested it got it then I'd be more than happy - we'd just add it
to our script to build it.

All the best!
- --
 Christopher Samuel Senior Systems Administrator
 VLSCI - Victorian Life Sciences Computation Initiative
 Email: samuel_at_[hidden] Phone: +61 (0)3 903 55545

Version: GnuPG v1.4.14 (GNU/Linux)
Comment: Using GnuPG with Thunderbird -