Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Bringing The Grid Home for Grid2008


Published on

Presentation for Bringing the Grid Home presented to Grid 2008. In this presentation I discuss my work G-ICING

Published in: Technology, Education
  • Be the first to comment

  • Be the first to like this

Bringing The Grid Home for Grid2008

  1. 1. Bringing the Grid Home Chris Sosa, Andrew Grimshaw University of Virginia October 1, 2008
  2. 2. Introduction
  3. 3. The Big Problem <ul><li>Grid has little uptake </li></ul>Hard to Use Inflexible Security Doesn’t play well with others
  4. 4. Solution Criteria
  5. 5. Bring in G-ICING <ul><li>Users and applications are familiar with the filesystem </li></ul><ul><li>Grid-backend will appear as a network drive to users </li></ul>
  6. 6. Talking to a Grid-Backend <ul><li>Resource Naming Service (RNS) </li></ul><ul><ul><li>Basic directory services </li></ul></ul><ul><ul><li>Entries may be added, deleted and listed </li></ul></ul><ul><li>ByteIO </li></ul><ul><ul><li>Provides POSIX-like interface to resources </li></ul></ul><ul><ul><li>Resources can be anything (database, a file, a host) </li></ul></ul><ul><li>Who else uses it? </li></ul><ul><ul><li>ByteIO interoperability fiesta – UVa, Fujitsu, EPCC, UNICORE </li></ul></ul><ul><ul><li>CERN has a working RNS with LFC and is working on a ByteIO implementation </li></ul></ul>
  7. 7. User to Kernel Communication <ul><li>DESIGN ALTERNATIVES </li></ul><ul><li>Local Procedure Calls </li></ul><ul><ul><li>Deprecated by MS </li></ul></ul><ul><ul><li>Calls are synchronous </li></ul></ul><ul><li>Inverted Call Model </li></ul><ul><ul><li>Takes advantage of the I/O mechanisms in WinNT </li></ul></ul><ul><ul><li>User level program makes special I/O Request: “Hello, I’m waiting for an operation” and Kernel mode stores it </li></ul></ul><ul><ul><li>Kernel forwards actual I/O requests, to the user mode by responding to the above I/O with the forwarded I/O call </li></ul></ul>
  8. 8. IFS Development in Windows
  9. 9. G-ICING Design
  10. 10. Kernel Management Service (KMS) <ul><li>Installable File System Driver </li></ul><ul><ul><li>Network Redirector </li></ul></ul><ul><ul><li>Kernel driver that interacts with other Kernel components </li></ul></ul><ul><li>Communicates to User-mode UFS with Inverted Call Model </li></ul>
  11. 11. User Forwarding Service (UFS) <ul><li>Uses JNI to communicate and forwards requests to GIS </li></ul><ul><li>Prompts user for credentials and obtains a delegated credential for use </li></ul>Flexible Security through Delegation
  12. 12. Grid Interface Service (GIS) <ul><li>Converts FS requests into ByteIO/RNS calls </li></ul><ul><li>Caches meta-information from ByteIO/RNS </li></ul><ul><li>Only interface to Grid-backend </li></ul>Meta-data Caching
  13. 13. Prototype in Action
  14. 14. Prototype in Action (Continued)
  15. 15. Evaluation <ul><li>Usability (compared to the alternatives) </li></ul><ul><ul><ul><li>Shell Extension (not app transparent) </li></ul></ul></ul><ul><ul><ul><li>Posix-like libraries (neither user or app transparent) </li></ul></ul></ul><ul><ul><ul><li>Special libraries – application transparent only if recompiled (can't with COTS or Legacy) </li></ul></ul></ul><ul><li>Security </li></ul><ul><ul><li>Depends on the Grid-backend but prototype is compatible with a flexible delegation model </li></ul></ul><ul><li>Standards – RNS, ByteIO </li></ul><ul><li>Performance – Coming up … </li></ul>
  16. 16. Performance Evaluation Setup <ul><li>Client </li></ul><ul><ul><li>Single-core 2.34 GHz desktop machine with 1GB memory running WinXP </li></ul></ul><ul><ul><li>100 Mbps connection </li></ul></ul><ul><li>Grid-Backend </li></ul><ul><ul><li>Genesis II running on seven 8-core Xeon processors running at 2.33 GHz with 16 GB memory </li></ul></ul><ul><ul><li>1 Gbps connection </li></ul></ul>
  17. 17. Performance Evaluation
  18. 18. Future Work <ul><li>Improve performance </li></ul><ul><ul><li>On-disk caching of data of both ByteIO and RNS data </li></ul></ul><ul><ul><li>Research in location-aware caching </li></ul></ul><ul><li>Implementation and Comparison to different FS mechanisms in other OSs </li></ul><ul><li>Stretching RNS / ByteIO interfaces to perform more Grid services </li></ul>
  19. 19. Conclusions <ul><li>Grids are still too difficult to use for both users and applications </li></ul><ul><li>Can extend the filesystem paradigm in Windows to bring the Grid to users </li></ul>
  20. 20. Related Work <ul><li>LUFS and FUSE are filesystem in user-space technologies for UNIX / Mac </li></ul><ul><ul><li>Lack support for Windows </li></ul></ul><ul><ul><li>Tied to UNIX security semantics </li></ul></ul><ul><li>Open AFS creates a modified Samba server but stuck to Samba/CIFS security model </li></ul><ul><li>Gfarm uses FUSE + syscall hook library </li></ul><ul><ul><li>Same problems with just FUSE </li></ul></ul><ul><ul><li>Overly complex for Windows, requires set up of a separate Linux box to forward messages through </li></ul></ul><ul><li>Glite provides POSIX-like interface that is neither user or application transparent </li></ul>
  21. 21. Questions <ul><li>? </li></ul>