1 / 15

IBP and Condor Micah Beck Assoc. Prof. & Director

Condor Week, Madison May 6, 2003. IBP and Condor Micah Beck Assoc. Prof. & Director. Funding Dept. of Energy SciDAC National Science Foundation ANIR UT Center for Info Technology Research. University of Tennessee Micah Beck James S. Plank Jack Dongarra

ninon
Download Presentation

IBP and Condor Micah Beck Assoc. Prof. & Director

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. Condor Week, Madison May 6, 2003 IBP and CondorMicah BeckAssoc. Prof. & Director

  2. Funding Dept. of Energy SciDAC National Science Foundation ANIR UT Center for Info Technology Research University of Tennessee Micah Beck James S. Plank Jack Dongarra University of California, Santa Barbara Rich Wolski Logistical Networking Research at UTK

  3. IBP: The Internet Backplane Protocol • A scalable mechanism for deploying shared storage resources throughout the network • A general store-and-forward overlay networking infrastructure • A state management infrastructure for distributed applications and active services

  4. The Network Storage Stack Applications • Our adaption of the network stack architecture for storage • Like the IP Stack • Each level encapsulates details from the lower levels, while still exposing details to higher levels Logistical File System Logistical Tools L-Bone exNode IBP Local Access Physical

  5. IBP: How it Works • Storage provisioned on community “depots” • Very primitive service (similar to block service, but more sharable) • Goal is to be a common platform (exposed) • Also part of end-to-end design • Best effort service – no heroic measures • Availability, reliability, security, performance • Allocations are time-limited! • Leases are respected, can be renewed • Permanent storage is to strong to share!

  6. The Network Storage Stack LoRS: The Logistical Runtime System: Aggregation tools and methodologies The L-bone: Resource Discovery & Proximity queries The exNode: A data structure for aggregation IBP: Allocating and managing network storage (like a network malloc)

  7. L-Bone: January 2003 Current Storage Capacity: 13 TB

  8. Multithreaded Transfers

  9. Caching/Staging

  10. Point-to-Multipoint

  11. Heterogeneous Multicast

  12. Relationship to Work of Condor Group • Wide Area File Management/Access • Management of Computation State • As a Storage Allocation Layer for • Kangaroo, NeSt • DiskRouter • If routers can have disks, how about disks with processors?

  13. Routers, Depots and the Network Functional Unit in in router send out NFU disk/RAM RAM execute in in in in store depot depot out out load

  14. Scalable Operations • IBP Depots with NFU define a State Transformation Substrate • Processes run at “endpoints” but can use NFUs to transform data in network • Is it processor-in-storage or active networking? • All state is exposed

  15. Logistical Computing and Internetworking http://loci.cs.utk.edu Micah Beckmbeck@cs.utk.edu

More Related