[Swift-devel] Swift Innovation for BOINC : Design Spec

[Xu Du]

Hi Ben,

The object of the project is to enable swift dispatch a job to BOINC. Currently, BOINC and Swift are independent.  BOINC has itself mechanism to manage the jobs( tasks),  it doesn't employ the shared file system. Simple speaking, a tasks will be created and the relate data (input files) will be put into BOINC Date Base when we submit a job to BOINC sever. In fact, there is no change on the files (including the executable program and the data) during so called "file transfer", what is done here is only to put the files to BOINC DB and register a new task on BOINC sever.  After a task submitted, BOINC server will handle the task, all BOINC clients connect with BOINC server, the procedure of BOINC system processing the task is transparent to Swift. 

Thanks,

Xu

----- Original Message ----- 
From: "Ben Clifford" <benc at hawaga.org.uk>
To: "Xu Du" <duxu at 263.net>
Cc: "Michael Wilde" <wilde at mcs.anl.gov>; <swift-devel at ci.uchicago.edu>
Sent: Tuesday, April 08, 2008 2:54 AM
Subject: Re: [Swift-devel] Swift Innovation for BOINC : Design Spec


> 
> Hi.
> 
> When running a program in Swift, there is a requirement that the input 
> files for a job are placed in the current working directory that the unix 
> process runs on.
> 
> Usually, that is achieved by using a shared filesystem between every 
> worker node. But, I think that in a BOINC deployment, there will not be a 
> shared filesystem that is shared between every worker node.
> 
> I see that you intend to do 'file transfer' with BOINC, but it is not 
> clear to me how those files will be connected with the jobs that want to 
> use them.
> 
> Is this addressed in your design?
> 
> -- 
> 
> 
>