1 / 5

DataSpace for ProActive Accessing and Managing Remote Files and Data

DataSpace for ProActive Accessing and Managing Remote Files and Data. Ankush Kapur , Kamran Qadir,Christian Delbe , Clement Mathieu Team: OASIS INRIA – Sophia Antipolis. Introduction. Goal - To provide a Global Virtual Data Space for ProActive applications. Project background:

dotty
Download Presentation

DataSpace for ProActive Accessing and Managing Remote Files and Data

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. DataSpace for ProActiveAccessing and Managing Remote Files and Data AnkushKapur, KamranQadir,ChristianDelbe, Clement Mathieu Team: OASIS INRIA – Sophia Antipolis

  2. Introduction • Goal - To provide a Global Virtual Data Space for ProActive applications. • Project background: • ProActive Deployment: • On-Demand creation of ProActive nodes. • Infrastructure independent applications. • Apache VFS API • Apache VFS provides a uniform view of files from different sources, such as local disk, http/ftp/sftp servers, zip and jar archives.

  3. A Simple Use Case ProActive Layer Active Object 1 Active Object 2 Active Object 3 Service Active Object Scratch1 Scratch3 Input File Output File Scratch2 Virtual File System Layer Write Virtual View Read

  4. Architecture/Current Progress Mount to VFS • At Node Deployment • At Active Object Creation • eg. /tmp/scratch/Node1eg. /tmp/scratch/Node2 • Global View of Scratch: VFS//GlobalScratch/Node1/AO1id/data1.txt .….…………………../Node2/AO2id/data2.txt NodeName, URI Node1 Node2 AO1 AO2 http http eg. /tmp/scratch/Node1/AO1id eg. /tmp/scratch/Node2/AO2id

  5. Further Work • Introduce a ProActive Provider • This provider will rely on ProActive connectivity, and • Lower level ProActive File Transfer operations. • Optimizing the Data Space • Integration of the Data Space with the deployment descriptor. • Provide support for Data Consistency • If Active Objects can write in other scratch directories, we have to maintain consistency between the files.

More Related