1 / 1

ScratchFS: A File System To Manage Scratch Disk Space For Grid Jobs

Batch Scheduler. End User. Worker Nodes. Job + Proxy. Grid Middleware. Computing Element. ScratchFS. Computing Center. proxy verification. ls /scratch/job/. ScratchFS. libfuse. Userspace. Kernel. VFS. FUSE. Ext3.

stacey-stuart
Download Presentation

ScratchFS: A File System To Manage Scratch Disk Space For Grid Jobs

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. Batch Scheduler End User Worker Nodes Job + Proxy Grid Middleware Computing Element ScratchFS Computing Center proxy verification ls /scratch/job/ ScratchFS libfuse Userspace Kernel VFS FUSE Ext3 ScratchFS: A File System To Manage Scratch Disk Space For Grid Jobs Leandro Franco and Fabio Hernandez IN2P3/CNRS Computing Centre Lyon, France Issues Since the actual operating systems were not designed to handle remote users in the way we conceive them in a grid world, we are obliged to use intermediate steps, like creating local accounts used to “convert” grid users to normal users. We are also forced to use different methods to monitor the space used by a job coming for the grid or to restrict the places where it can operate. • Features of ScratchFS • Implemented in user space (no kernel modifications needed). • Quota enforcement ( transparent to the users). • Life time management. • Real time usage details. • Security based on grid proxies instead of Unix users. • Grid Security • All the security can be controlled independently of the user id that runs the job. • Different grid jobs running under the same user id will be recognized as different jobs belonging to different owners. • A mapping from grid certificates to local identifiers is no longer needed. Performance The performance tests showed us that although there is a price to pay for the functionality, it is not extremely high. Specially if it is compared to existing sandboxes or similar file systems. http://grid.in2p3.fr/scratchfs

More Related