Create some kind of "push" system to let MTT start as soon as the nightly tarballs are made

[ompiteam]

Talking with IU a bit, it seems desirable to be able to make some kind of "push" system that would allow starting MTT very shortly after the nightly tarballs are made (rather than checking for a new tarball at some arbitrary point in the middle of the night).

This may involve two parts:

• The IU server publishing its current status -- more than just the latest snapshot available (which is what is currently available). Perhaps the server can advertise the next time it plans to try to make a tarball, that it's currently trying to make a tarball, etc. This is not really an MTT issue, but is worth noting here for the interaction described below (i.e., the MTT client will need to interact with this published status from the IU server).
• The OMPI MPI Get module can check this status, and perhaps upon trigger from an INI file field, loop over checking for a new tarball, waiting for that tarball. Specifically:
  • The MTT client could be put into an "infinite" mode -- after a successful "MPI Get" phase, it would do all the rest of the phases.
  • But then instead of quitting, the client would then loop around and block in MPI Get waiting for the next tarball
  • Based on information published by the IU server, it could know when to start pinging and asking for a new tarball, and it could sleep until then.
  • At the designated time, the MTT client can wake up and ask the server if it's got a new tarball yet. The server will have published "I'm making a new tarball now... please wait..." so the MTT client can check every 5 minutes or so.
  • Once a new tarball has been made, the server changes its status to reflect the new tarball. The MTT client will see this, download the tarball, and go through its entire sequence (eventually ending up in MPI Get again, blocking waiting for the ''next'' tarball).
  • If a new tarball is not made (e.g., an error, or there were no changes to SVN that warranted making a new tarball), the IU server just changes its status to reflect when the next attempt at making a tarball would be. The MTT client will see that no new tarball was issued, and will go back to sleep until the next time that the IU server has advertised that it will make a new tarball.
  • This can all happen on a per-series basis (e.g., the IU server can individually publish its status for the 1.0, 1.1, 1.2, and trunk tarballs).

[ompiteam]

Imported from trac issue 126. Created by jsquyres on 2006-11-01T17:30:04, last modified: 2007-09-11T15:03:36

[ompiteam]

Trac comment by jsquyres on 2007-01-12 17:52:03:

Moving this to 2.1.

[ompiteam]

Trac comment by emallove on 2007-02-28 11:26:27:

Milestone v2.1 deleted