|
|
This is only a preview of the paper
Click here to register and get the full text.
Existing members click here to login
|
|
|
... The first was to present an application, Video IBP ster, built using the tools of the Network Storage Stack that delivers DVD-quality video without dropping frames, without losing data and without specialized multi-media streaming servers. ... The second goal was to determine performance limits when using multiple, untuned TCP streams to retrieve a striped and replicated file across a long network. Since tools built using the Network Storage Stack allow striped downloads from multiple servers in parallel and since the client machines were all connected to Gigabit Ethernet (GigE), we hoped that we would observe a linear scale up of throughput when downloading from multiple servers. ... We had two goals: the first was to demonstrate Video IBP ster, which is a multi-media streaming application built using components from the Network Storage Stack. ... The paper is organized as follows: In section 2 we provide a brief overview of the Network Storage Stack and Logistical Runtime System, which is our infrastructure test bed. ...
2 The Network Storage Stack
The tools that we used for the demo and for testing are based on the Network Storage Stack, developed at the University of Tennessee [ASP+02]. The goal of the Network Storage Stack (Fig-ure 1) is to layer abstractions of network storage that allow writable storage resources to be part of the wide-area network in an efficient, flexible, sharable and scalable way. ... 1 IBP
The lowest layer of the storage stack that is globally accessible from the network is the Internet Backplane Protocol (IBP) [PBB! ... IBP is server daemon software and a client library that allows storage owners to insert their storage into the network, and to allow generic clients to allocate and use this storage. The unit of storage is a time-limited, append-only byte-array. WithIBP, byte-array allocation is like a network malloc() call — clients may request an allocation from a specific IBP storage server (or depot), and if successful, are returned trios of cryptographically secure text strings (called “capabilities”) for reading, writing and management. Capabilities may be used by any client in the network, and may be passed freely from client to client, much like a URL.
IBP does its job as a low-level layer in the storage stack. It abstracts away many details of
the underlying physical storage layers: block sizes, storage media, control software, etc. However, it also exposes many details of the underlying storage, such as network location, network transience and the ability to fail, so that higher layers in the stack may abstract these more effectively. ... IBP depots register themselves with the L-Bone, and clients maythen query the L-Bone for depots that have various characteristics, including minimum storage capacity and duration requirements, and basic proximity requirements. For example, clients may request an ordered list of depots that are close to a specified city, airport, US zipcode, or network host. Once the client has a list of IBP depots, it may then request that the L-Bone use the Network Weather Service (NWS) [WSH99] to order those depots according to bandwidth predictions using live networking data. Thus, while IBP gives clients access to remote storage resources, it has no features to aid the client in figuring out which storage resources to employ. ... Thus, the exNode allows users and applications to create network files out of time-limited and failure-prone IBP allocations in such a way that much stronger properties (e. ... Like IBP capabilities, they may be passed from client to client, anywhere in the network, with no registration from a central authority.
Approximate Word count = 2933
Approximate Pages = 11.7
(250 words per page double spaced)
|
|
|
|
|
|