[Swift-devel] coasters

[Mihael Hategan]

I committed a preliminary coaster code to SVN. It's called
provider-coaster, and it works pretty much like any other provider, with
the following notes:

The job manager is made of 2 or 3 parts:
<coasting-provider>:<remote-provider>[:<remote-job-manager>].

So if you want to, say, start the service on teraport using gt2, then
start workers using gt4 on PBS, you'd say: jobManager="gt2:gt4:pbs". Or
if you wanted to start the service with ssh and then use the local (to
the service) pbs provider to start workers, it would be
jobManager="ssh:pbs".

It's missing a bunch of things. One of them is that the service, once
started, won't shut down by itself, so you should log into the machine
you started it on, and kill it. Another is a better strategy for
allocating workers than "as many as there are jobs". And so on...

org.globus.cog.abstraction.impl.execution.coaster.JobSubmissionTaskHandler.main() contains some code to test this. Please be careful if running on a cluster: don't submit too many jobs.