[Swift-devel] Fwd: Re: chained genU workflow

[Ben Clifford]

On Tue, 1 May 2007, Mihael Hategan wrote:

These should probably go into the bugzilla as they look like app 
requirements that need tracking.


> - MPI jobs with the PBS provider. They need to be able to run with more
> than one version of MPI.

> - Easier configuration of tc.data/sites.xml. Basically they need the
> ability to use a global sites.xml while changing only things like the
> project profile entry.

It maybe makes sense in general that a commandline specified value 
overrides a tc.data-specified value which overrides a sites.xml-specified 
value.

Though in this 'project' situation, that might look wrong in the 
multi-site case (though, given that they're using PBS on single site, that 
isn't so much a problem at the moment)

> - The cleanup didn't work as it was. It would submit a job on the
> default execution provider (whatever that was) which needed a project
> profile entry, but the swift library didn't provide one. This was solved
> by hacking the vdl lib and adding /bin/rm in tc.data.

mmm hacks.

anything useful from a production codebase perspective?

> - They would like the cleanup to be done without pbs in the future
> (possibly fork or directly with the fileop provider). There's some
> thinking that needs to go here.

VDS1's sites descriptions allowed different job submission mechanisms to 
be specified for different purposes - the 'vanilla' universe and the 
'transfer' universe with the intention that the vanilla universe is for 
running the meat of the workflow and would point at a batch system of some 
kind, whilst the transfer universe is intended for lighter weight jobs and 
would point at GRAM2's jobmanager-fork.

That's perhaps a starting point.

--