May be I'm not getting it right: what's the alternative use-scenario where GT5 targets to solve?
On 11/19/2012 at 4:10 AM, "Ian Foster" wrote:I think that BOINC is what you are looking for. Or Condor. On Nov 18, 2012, at 5:52 PM, [email protected] wrote: Greetings GT community, Suppose that a pool of computers are able to donate their idle CPU time, how can a problem (i.e. an piece of code) get executed in them in a distributed manner? For example, when I use the command globus-job-submit, or globus-job-run, how will my local machine know where should these jobs to be submitted? I'm expecting that every resource should register itself to a discovery data base (service) that is hosted on a server(s). And that grid users (e.g. programmers/researchers) submit problems, they submit it somewhere that will dispatch them to multiple resources (CPU donators) according to a scheduler and an execution management plan that decies what to do in case of a failure. However, I fail to see how the above thoughts map to GT5 after following my reading of the quick start guide in http://www.globus.org/toolkit/docs/5.2/5.2.2/admin/quickstart/ -- what is in the guide is pretty controlled by the user/programmer (e.g. he specifies which computer to execute which commands on). Rgrds,J
