| 1 |
This architecture is more general than that needed to support MPI like parallel computing
-
It includes ideas present in systems like Condor and Javelin
|
| 2 |
The diagram only shows server (bottom) and service (top) layers. There is of course a client layer which communicates directly with "Parallel Computing (PC) Control and Services module"
|
| 3 |
We assume that each workstation has a "Jini client" called here a "Jini Parallel Computing (PC) Embryo" which registers the availability of that workstation to run either particular or generic applications
-
We do not use term Jini client as this is confusing with client machines of users
-
The Jini embryo can represent the machine (I.e. ability to run general applications) or particular software
|
| 4 |
The Gateway or "Parallel Computing (PC) Control and Services module" queries Jini lookup server to find appropriate service computers to run a particular MPI job
-
It could of course use this mechanism "just" to be able to run a single job or to set up a farm of independent workers
|
