1 / 6

Wide-Area File Systems Status Overview

Wide-Area File Systems Status Overview. Chris Jordan. GPFS-WAN. Steady State – in production on multiple resources Little prospect of additional resources due to licensing Should continue for the foreseeable future. Lustre-WAN Efforts. Indiana “DC-WAN” – Lustre 1.6

berget
Télécharger la présentation

Wide-Area File Systems Status Overview

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. Wide-Area File SystemsStatus Overview Chris Jordan

  2. GPFS-WAN • Steady State – in production on multiple resources • Little prospect of additional resources due to licensing • Should continue for the foreseeable future

  3. Lustre-WAN Efforts • Indiana “DC-WAN” – Lustre 1.6 • In Production on multiple resources • PSC “J-WAN” – Lustre 2.0 (alpha) • Deployed at multiple sites, not in production • Issues for WAN-File systems • Identity Mapping • Storage Locality • Hierarchical Storage • Non-Native Access

  4. Indiana “DC-WAN” • In production for over a year on multiple TeraGrid resources • IU BigRed, PSC Pople, TACC Lonestar • Tested on Cobalt, Abe, QueenBee • Uses custom identity-mapping tables (similar to grid-mapfile) • Uses “stock” Lustre releases, has broadest compatibility • Does not have storage locality support • Interest in hierarchical storage when Lustre supports it

  5. PSC “J-WAN” • In development for over a year with multiple sites • PSC, SDSC, NICS • Uses Lustre “head” tree for eventual 2.0 release • Not ready for production, not compatible with most cluster installs at the current time • Uses Kerberos for identity mapping • Storage “pools” but not hierarchical storage • Remains promising but production timeline is not clear • Currently too little capacity to be useful (4TB)

  6. Where do we go from here? • What are we trying to do? • Distributed file systems have demonstrated value to users • Global file systems are the “holy grail” of WAN-FS • Also need persistent disk resources with more flexible usage patterns • Push to mount DC-WAN everywhere it is possible? • Push to add NFS/pNFS mounts as well? • Add storage to DC-WAN and allocate it? • Add storage to J-WAN? Where?

More Related