Open MPI logo

MTT Devel Mailing List Archives

  |   Home   |   Support   |   FAQ   |   all MTT Users mailing list

From: Jeff Squyres \(jsquyres\) (jsquyres_at_[hidden])
Date: 2006-06-28 15:46:58


> -----Original Message-----
> From: mtt-users-bounces_at_[hidden]
> [mailto:mtt-users-bounces_at_[hidden]] On Behalf Of Ethan Mallove
> Sent: Wednesday, June 28, 2006 12:56 PM
> To: General user list for the MPI Testing Tool
> Subject: [MTT users] Run MTT with pre-built ompi
>
> I want to skip the MPI Get and Install phases, and simply
> point MTT to
> my pre-built/installed Open MPI. Can this be done in the .ini
> file, or
> do I need to create a whole module to do this? I thought that just
> inserting "installdir = /my/ompi/installation" in the [MPI
> Install: foo]
> section would do that. I also created a Null.pm module that
> does nothing
> (contents: "1;") so MTT would bark at me for not supplying a module
> parameter.
>
> I must be missing something.

No, you're not missing anything. :-)

We had actually talked about this feature but not implemented it yet.
This is in the TODO file listed under:

--developer switch - run MTT against a current install

the intent of which was to do pretty much exactly what you described.
The pieces that are missing are that MTT pretty much needs the MPI Get
and Install phases, if for nothing other than installing the Right
meta-data in its data structures so that it "knows" about that OMPI
installation.

So we might want to add Get and Install modules that do nothing in terms
of the scratch tree, but end up providing enough meta information that
they can be added to the xml files. These are not "Null" modules,
strictly speaking, because they need to extract name, version,
directory, etc. information (some of which is probably OMPI-specific).

Make sense?

-- 
Jeff Squyres
Server Virtualization Business Unit
Cisco Systems