<html><body>
<p>Most discussion I have heard relates to how a running job that makes a decision, at a well defined point, to grow itself can do that. The MPI standard currently tries to cover the aspects of this which fit within a library model and leave the resource manager outside the standard. <br>
<br>
This does not seem to be your focus. Tell me if I have misunderstood.<br>
<br>
You seem to be interested in the situation where resources are added to a cluster (or maybe freed up by other jobs completing) and having a running MPI job get notified asynchronously that there are newly available resources it can make a bid for. This idea of the cluster manager pushing resources to a job without regard to where the job is in its execution would bring lots of new issues. I am not aware of anybody having made a serious attempt to even define what would be needed inside the MPI standard to let applications catch and act on an asynchronous notification like this. <br>
<br>
My first guess is that pushing an offer of additional resource would not be very hard to design into a resource manager but the MPI API side of how to react asynchronously to that offer would be very complex.<br>
<br>
Either way (Running job decides to try for more resource vs resource manager tries to volunteer more resource to running job) I think the MPI standard can not try to specify very much about how the resource manager does its part.<br>
<br>
<br>
Dick Treumann - MPI Team <br>
IBM Systems & Technology Group<br>
Dept X2ZA / MS P963 -- 2455 South Road -- Poughkeepsie, NY 12601<br>
Tele (845) 433-7846 Fax (845) 433-8363<br>
<br>
<br>
<tt><snip></tt><br>
<br>
<tt>> As you said, That paragraph is in the context of process creating <br>
> and yes! my question was about runtime reconfiguration of an MPI <br>
> cluster (whole) based on dynamic application requirements. But I <br>
> think that would be impossible without having a flexible resource <br>
> control. When a new node joins a cluster some pre-works must be done<br>
> to enable that new node act as a member of that cluster (in run <br>
> time), also, some one must be informed about new resources which <br>
> just have been added to the cluster by entrance of new node and I <br>
> think all these preparations need that missing flexible resource manager.</tt><br>
<tt>> </tt><br>
<tt>> </tt><br>
<tt>> </tt><br>
<tt>> Regards,</tt><br>
<tt>> Siavash_______________________________________________<br>
> mpi-22 mailing list<br>
> mpi-22@lists.mpi-forum.org<br>
> <a href="http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-22">http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-22</a><br>
</tt></body></html>