[openfabrics-ewg] OpenMPI package

Gilad Shainer Shainer at Mellanox.com
Thu Mar 23 09:09:22 PST 2006


 - What is the plan for having 2 MPIs in this distribution -- how will
users/sysadmins choose between them?  I.e., are we going to allow both to be
installed and make it a user-level decision which to use?  Or will the
sysadmin only pick one to install?  >Or ...?

<Aviram> We need to decide on that. All, how do you view it?

<Gilad> The simplest way is to let the sysadmin pick one of the two to
install. 


-----Original Message-----
From: Aviram Gutman 
Sent: Thursday, March 23, 2006 8:35 AM
To: Jeff Squyres (jsquyres); Moni Levy
Cc: Pavel Shamis; Gil Bloch; openfabrics-ewg at openib.org; Gleb Natapov
Subject: RE: [openfabrics-ewg] OpenMPI package


Hi Jeff,

Welcome aboard. Tziporet is out this week. I tried to answer most of the
questions below. We'll get back to you wit the rest of the answers by Monday
morning. Please See some answers below. 


Regards,
   Aviram

-----Original Message-----
From: Jeff Squyres (jsquyres) [mailto:jsquyres at cisco.com]
Sent: Thursday, March 23, 2006 3:41 PM
To: Aviram Gutman; Moni Levy
Cc: openfabrics-ewg at openib.org; Gleb Natapov
Subject: RE: [openfabrics-ewg] OpenMPI package

Several issues:

1. Since I am just entering this effort, I downloaded RC2 yesterday and
poked around inside for details on how Open MPI will need to be packaged.  I
sent an off-list mail to Tziporet last night asking a bunch of technical
questions (I probably should have sent this on-list, sorry).  Here are the
main questions from that e-mail:

- I downloaded RC2.  It looks like you are distributing source and have some
scripts to build RPMs and install the RPMs.  Is that correct / the goal of
IBED?

<Aviram> Yes

- The README appears to be quite out of date; I assume you will need some
Open MPI-specific information for it.  How should I get this to you?

<Aviram> Just send it and we'll incorporate it.

- It looks like the LICENSE file is incomplete -- shouldn't it contain at
least references to the license / copyright information of the sub-packages?
(e.g., MVAPICH and others)

<Aviram> That is good issue. I am not a LICENSE expert. Who can answer it?
Marketing guys? 

- I see a bunch of top-level *.sh scripts -- these will need to be expanded
for Open MPI.  Who does that -- me or you?

<Aviram> Can you do it and send it over?

- I see SOURCES/mpi_osu...tgz.  That contains a bunch of scripts and the
mvapich tarball.  I'm assuming that Open MPI needs to be bundled this way as
well...?  Is this documented anywhere?  Is there a reason why a tarball
contains another tarball?


- The mpi_osu...tgz file contains several MPI-independent utilities (PMB,
prestal, etc.).  Should these be moved out of the OSU MPI tarball and into
an MPI-agnostic tarball, and then compiled against each MPI that is
installed?

<Aviram> Will get back to you on those two.

- What is the plan for having 2 MPIs in this distribution -- how will
users/sysadmins choose between them?  I.e., are we going to allow both to be
installed and make it a user-level decision which to use?  Or will the
sysadmin only pick one to install?  Or ...?

<Aviram> We need to decide on that. All, how do you view it?

2. Some more questions that I did not include in my mail last night:

- Is there a source code repository for IBED somewhere?  What is the model
for developers to modify / test IBED?

- What version of MVAPICH is being used?  I see
mvapich-0.9.5-mlx2.0.1.tar.gz -- does this mean it's Mellanox's v2.0.1 of
MVAPICH 0.9.5?  Are other vendors allowed to modify this?  (I ask because
all of our MVAPICH's are slightly different -- fixed bugs specific to our
customers, etc.)

<Aviram> We'll use 0.9.7 It will be incorporated on the next rc. Yes we can
fix and modify it.

- There appear to be multiple levels of indirection in the MVAPICH build
scripts -- what directory --prefix is it being installed to?  (this is going
to be influenced by the answer to the "2 MPI" question, above)

<Aviram> Will get back to you it.

3. I would like to use Open MPI v1.0.2 for the IBED release (Gleb is on the
Open MPI mailing lists and probably saw me send that intention to the Open
MPI team yesterday).

<Aviram> OK. 

4. Gleb sent me a proposed spec file for Open MPI -- we'll iterate about
this off-list.

<Aviram> Who will send us the OpenMPI version to be integrated?


> -----Original Message-----
> From: Aviram Gutman [mailto:aviram at mellanox.co.il]
> Sent: Thursday, March 23, 2006 12:47 AM
> To: Moni Levy; Jeff Squyres (jsquyres)
> Cc: openfabrics-ewg at openib.org; Gleb Natapov
> Subject: RE: [openfabrics-ewg] OpenMPI package
> 
> 
> Jeff, Moni,
> 
> We want to integrate to the IBED package OpenMPI. We need an agreement

> on the package. Can we converge on which OpenMPI version to take this 
> week?
> Thus, we can release a new rc next week with OpenMPI.
> 
> 
> Regards,
>    Aviram
> 
> -----Original Message-----
> From: openfabrics-ewg-bounces at openib.org
> [mailto:openfabrics-ewg-bounces at openib.org] On Behalf Of Moni Levy
> Sent: Thursday, March 23, 2006 10:32 AM
> To: jsquyres at cisco.com
> Cc: openfabrics-ewg at openib.org; Gleb Natapov
> Subject: [openfabrics-ewg] OpenMPI package
> 
> Hi, Jeff,
>     I would like to share with you that there was request for a 
> OpenMPI package that will enable us to test it and later integrate it 
> into the build framework for the next RC of the EOD release. Voltaire 
> (Gleb
> Natapov) picked up the glove and generated such a package. It may be 
> used as a reference for future packaging that I'm sure you'd like to 
> implement.
> 
> Best regards,
> Moni
> 


_______________________________________________
openfabrics-ewg mailing list
openfabrics-ewg at openib.org
http://openib.org/mailman/listinfo/openfabrics-ewg
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openfabrics.org/pipermail/ewg/attachments/20060323/0631b3be/attachment.html>


More information about the ewg mailing list