1 / 20

Genesis II: Mapping Grids into the Local File System: Access, RNS, and ByteIO

“Open Source, OGSA Implementation”. Genesis II: Mapping Grids into the Local File System: Access, RNS, and ByteIO. Andrew Grimshaw Genesis II Team University of Virginia. Outline. Background Genesis II - The specs in action. Access Layer. Grid Services Layer. Resources Layer.

cliff
Download Presentation

Genesis II: Mapping Grids into the Local File System: Access, RNS, and ByteIO

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. “Open Source, OGSA Implementation” Genesis II:Mapping Grids into the Local File System: Access, RNS, and ByteIO Andrew Grimshaw Genesis II Team University of Virginia Genesis II “Open Source, OGSA Implementation”

  2. Outline • Background • Genesis II - The specs in action Genesis II “Open Source, OGSA Implementation”

  3. Access Layer Grid Services Layer Resources Layer API’s & interfaces, e.g. SAGA, NFS, CIFS Standard portypes Classic three layer view Genesis II “Open Source, OGSA Implementation”

  4. Classic 3-layer name scheme Abstract name: EPI, rebinding Human names RNS file name 1 File replica 1 … WS-name EPR File replica 2 RNS file name n … File replica m This is essentially a table WS-Names are WS-Addresses with optional EPI and resolver EPR Genesis II “Open Source, OGSA Implementation”

  5. Four specs • RNS – directory service that maps strings to EPRs <<EPR> XSD-any> • Can build directed graphs, including trees • Leaves can be most anything, web pages, ByteIO endpoints, DMI endpoints, BES resources • WS-Naming – A profile on WS-Addressing that supports identity and rebinding of addresses – migration, failure, and replication transparency • ByteIO – think POSIX file/steam, read, write, stat • BES – Accepts JSDL documents and executes them Genesis II “Open Source, OGSA Implementation”

  6. Outline • Background • Genesis II – The specs in action Genesis II “Open Source, OGSA Implementation”

  7. User’s First • A large percentage of a grid’s target audience is unable or unwilling to learn new interaction abstractions • Instead of asking the user to adapt to the grid, we should adapt the grid to the user Genesis II “Open Source, OGSA Implementation”

  8. User Abstractions • One of the most ubiquitous user interaction abstractions is the file system • Drag-and-drop • Double Click • /proc filesystem • Named pipes • RNS, ByteIO, and WS-Naming provide the foundation for building these abstractions Genesis II “Open Source, OGSA Implementation”

  9. (Most) everything is a file or directory • Files and directories can be accessed without knowing anything about Grids, Web Services, or anything thanks to OGRSH/IFS • OGRSH/IFS map the Grid into the file system • BES resources, queues are directories • “ls” to list the jobs, “cat” a job to see its state • “cp” a JSDL file into the directory -> start the job up • A shell script can start jobs by copying • Genesis II containers are directories • “ls” to see the services and porttypes • IDP are files/directories • IS’s are directories • “cp” a query file to IS, creates result • RDBMS’s will be directories • The user can access all of these services without dealing with Web Services!! Genesis II “Open Source, OGSA Implementation”

  10. Genesis II - Data • FTPd for Windows • OGRSH for Linux (shim) • IFS for Windows • ExportDir • Replicated ExportDir Genesis II “Open Source, OGSA Implementation”

  11. Localhost Fdpd • Fully secure • My X.509 • SSL • No bits in the clear Genesis II “Open Source, OGSA Implementation”

  12. Windows IFS Genesis II “Open Source, OGSA Implementation”

  13. OGRSH (Linux) Genesis II “Open Source, OGSA Implementation”

  14. Using RNS to name non-file-system components • BES resources are also RNS directories • We can schedule a job on a resource simply by “dropping” it into the directory Genesis II “Open Source, OGSA Implementation”

  15. Export Directory • Map a Unix or Windows file system into the Genesis II RNS name space so that others can securely Create/Read/Write/Destroy Genesis II “Open Source, OGSA Implementation”

  16. Mapping data into the Grid • Links directories and files from source location to data grid directory and user-specified name • Presents unified view of the data across platforms, locations, domains, etc. • Data publisher controls authorization policy. Data clients Data clients Data publisher Data publisher Data publisher Windows Windows Linux Genesis II “Open Source, OGSA Implementation”

  17. Export Directory Tool Genesis II “Open Source, OGSA Implementation”

  18. Create an Export DirSelect local path Genesis II “Open Source, OGSA Implementation”

  19. Create an Export DirSelect target RNS path Genesis II “Open Source, OGSA Implementation”

  20. Moral of the story • RNS allows us to place arbitrary resources into a traditional directed graph/tree structure • OGRSH/IFS map RNS namespaces into the local file system • Users can interact with the grid without knowing anything about grids Genesis II “Open Source, OGSA Implementation”

More Related