Bringing the Grid Home  Chris Sosa, Andrew Grimshaw University of Virginia October 1, 2008
Introduction
The Big Problem <ul><li>Grid has little uptake </li></ul>Hard to Use Inflexible Security Doesn’t play well  with others
Solution Criteria
Bring in G-ICING <ul><li>Users and applications are familiar with the filesystem </li></ul><ul><li>Grid-backend will appea...
Talking to a Grid-Backend <ul><li>Resource Naming Service (RNS) </li></ul><ul><ul><li>Basic directory services </li></ul><...
User to Kernel Communication <ul><li>DESIGN ALTERNATIVES </li></ul><ul><li>Local Procedure Calls </li></ul><ul><ul><li>Dep...
IFS Development in Windows
G-ICING Design
Kernel Management Service (KMS) <ul><li>Installable File System Driver </li></ul><ul><ul><li>Network Redirector </li></ul>...
User Forwarding Service (UFS) <ul><li>Uses JNI to communicate and forwards requests to GIS </li></ul><ul><li>Prompts user ...
Grid Interface Service (GIS) <ul><li>Converts FS requests into ByteIO/RNS calls </li></ul><ul><li>Caches meta-information ...
Prototype in Action
Prototype in Action (Continued)
Evaluation <ul><li>Usability (compared to the alternatives) </li></ul><ul><ul><ul><li>Shell Extension (not app transparent...
Performance Evaluation Setup <ul><li>Client </li></ul><ul><ul><li>Single-core 2.34 GHz desktop machine with 1GB memory run...
Performance Evaluation
Future Work <ul><li>Improve performance </li></ul><ul><ul><li>On-disk caching of data of both ByteIO and RNS data </li></u...
Conclusions <ul><li>Grids are still too difficult to use for both users and applications </li></ul><ul><li>Can extend the ...
Related Work <ul><li>LUFS and FUSE are filesystem in user-space technologies for UNIX / Mac </li></ul><ul><ul><li>Lack sup...
Questions <ul><li>? </li></ul>
Upcoming SlideShare
Loading in …5
×

Bringing The Grid Home for Grid2008

495 views
437 views

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
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
495
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
2
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Good afternoon and Konichiwa Today I’ll be talking about G-ICING, an Installable File System for Windows that interfaces with a Grid-Backend. As this photo shows, G-ICING is intended to be a layer on top of the Grid intended to make the grid tastier ;-)
  • Explosion of information systems has led to vast arrays of data stored in widely varying formats, locations, and subject to numerous access and privacy policies. Collected and housed in standalone data stores with little or no integration between systems. Definte interest in more integrations resources. Introduce the grid, integrating information across organizational boundaries. Requires tackling a wide range of issues including finding, naming and accessing, crossing firewalls, enforcing policies, et al. Grid was supposed to solve all this (move with slide)
  • Simple and familiar - users should use a familiar paradigm. Users do not like to change the way they work, instead we should extend existing paradigms to interact with the Grid rather than vice versa COTS and legacy applications do not change. We must use something that they already use Performance, we just can’t die here Security – same shpeal Standards in order to interact with others People don’t want to be locked into one vendor. Help innovate on a grand scale since everyone can talk to each other Don’t have to develop same things more than once to take advantage of others sharing resources. Simple and familiar User Transparency Application Transparency We FORGET this criterion often Performance Users and applications don’t like to wait around all day Security Organizations need to enforce policies Normal users need it Based on Standards to allow interaction between different Grid infrastructures
  • More FOCUS Talk about how people and applications are familiar with the filesystem interface. Talk about how the IFS transparently maps the Grid into the Windows file system (DO NOT GLOSS OVER SOS-KAY).
  • Uva, Fujitsu, EPCC (Edinburgh), UNICORE
  • Focus on more Inv Call Model
  • Security – within the host G-icing relies upon Windows security to protection information between users of the same machine. Host-grid secuirty is complex. G-icing acts as a proxy for users. GIS prompts user for credentials and user is given a choice of using one of their certificates. GIS gets a signed delegated credential. Uses WS-Security* family of specifications and profiles.
  • We knew would be slow. Overhead involved with WS is enormous. Multiple XML serialization and deserialization ops with signing and encryption. A factor slower (10x)‏
  • 3 – double clicking on an application etc
  • 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>

    ×