Subject: Re: [MTT users] To run MTT on our cluster
From: Jeff Squyres (jsquyres) (jsquyres_at_[hidden])
Date: 2014-05-29 09:17:58
I think Ralph and Gilles covered most everything, just let me emphasize a few things:
- MTT is simply an engine for running tests and gathering results. Nothing more.
- MTT actually only includes a trivial test suite for MPI ("hello world" and "send a message around in a ring").
- In the Open MPI community project, we have a closed SVN repo for our convenience that includes a whole pile of test suites that we run via MTT. It's a close repo because we don't own the redistribution rights to most of the test suites (e.g., NetPIPE, IMB, OSU, ...etc.).
- You absolutely can download these test suites yourself from the greater internet and run them via MTT. There is nothing magical about our closed SVN repo; it's purely for our own convenience.
- The MTT web reporter we have at http://mtt.open-mpi.org/ is for us to monitor the development of Open MPI itself.
I've seen other admins do what you're proposing (use MTT for MPI/health checking of your cluster). While there's a bit of a learning curve, MTT is actually pretty great at that kind of stuff -- it can run dozens/hundreds/thousands of tests in an automated fashion and then report the results to a central location (e.g., email, file, and/or your own internal instance of the MTT database/web reporter).
One other piece of information that may be helpful: a key piece of knowledge that we learned while developing MTT is that every organization wants to do their testing differently. That's why there's so many CLI and configurable options to MTT.
Hope that helps!
On May 28, 2014, at 11:29 PM, Jaison Mulerikkal <j.mulerikkal_at_[hidden]> wrote:
> Hi Ralph,
>
> Thanks for your previous clarification.
>
> At our organisation (www.nesi.org.nz) we would like to use MTT for MPI heath check of our clusters. It it okay use MTT, legally, if we sign up to the following agreement.
> http://www.open-mpi.org/community/contribute/corporate.php. Whom shall I send this doc?
>
> If that is done, how can we install MTT in our clusters? Can you please explain it to me step by step? Or is there any elaborate documentation to get info on it? I have gone through the MTT wiki. It doesn’t explicitly speak about how MTT can be deployed in a stand-alone cluster like ours.
>
> We are using Easy-Build to install MPI and other libraries. So we may skip those steps in MTT.We just need to run the tests and collect health reports. From what I understand from the documentation, I have to fetch MPI tests from your svn server each time and run it on our machines. Can we collect the results internally and use MTT Reviewer internally to assess it? Or does it go to a central server outside our organisation?
>
> Can you please help us through these queries? Thanks in advance.
>
> Jaison Mulerikkal, PhD
> New Zealand eScience Infrastructure
> The University of Auckland
> e: j.mulerikkal_at_[hidden]
> p: +64 9 923 2194 (internal ext: 82194)
> w: www.jaison.me
>
>
>
>
>
> On 23/05/2014, at 3:49 pm, Ralph Castain <rhc_at_[hidden]> wrote:
>
>> I do it all the time myself - the ini file contains this:
>>
>> #======================================================================
>> # MPI get phase
>> #======================================================================
>>
>> #----------------------------------------------------------------------
>>
>> [MPI get: My Installation]
>> mpi_details = Open MPI
>> # Leave this parameter blank to
>> # have MTT search your path for an MPI
>> # alreadyinstalled_dir = /your/installation
>> module = AlreadyInstalled
>>
>>
>> #----------------------------------------------------------------------
>>
>> [MPI install: My Installation]
>> mpi_get = My Installation
>> module = Analyze::OMPI
>>
>>
>> Everything else proceeds the same
>>
>>
>> On May 22, 2014, at 8:14 PM, Jaison Mulerikkal <j.mulerikkal_at_[hidden]> wrote:
>>
>>> Hi,
>>>
>>> I am just referring to the following previous query at MTT forums, because I too has a similar requirement.
>>>
>>> -----------------------
>>> 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
>>>
>>> http://www.open-mpi.org/community/lists/mtt-users/2006/06/0013.php
>>> ———————————
>>>
>>> The reply mentioned that this functionality was in your TODO list. Have you implemented it in anyway at all?
>>>
>>> We are running a HPC cluster and we use easy-build to make our modules (including MPI) available to our users. So we may not want to Get, Install, Build steps at MTT, but the Run section to test the stability of the systems. Is it possible to do?
>>>
>>> Thanking you in advance,
>>>
>>> Jaison Mulerikkal
>>> New Zealand eScience Infrastructure
>>> The University of Auckland
>>> e: j.mulerikkal_at_[hidden]
>>> p: +64 9 923 2194 (internal ext: 82194)
>>> w: www.jaison.me
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> mtt-users mailing list
>>> mtt-users_at_[hidden]
>>> http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users
>>
>> _______________________________________________
>> mtt-users mailing list
>> mtt-users_at_[hidden]
>> http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users
>
> _______________________________________________
> mtt-users mailing list
> mtt-users_at_[hidden]
> http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users
-- Jeff Squyres jsquyres_at_[hidden] For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/