We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

Network Block Device how, what, why

Formal Metadata

Title
Network Block Device how, what, why
Title of Series
Number of Parts
611
Author
License
CC Attribution 2.0 Belgium:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor.
Identifiers
Publisher
Release Date
Language
Production Year2017

Content Metadata

Subject Area
Genre
Abstract
This talk will describe the NBD protocol: what is it, what can it do, and whyis it relevant for virtualization and IaaS. We will also touch at a fewfeatures that have been specified for the protocol, but so far have not beenimplemented in any known implementation. The Network Block Device (NBD) was originally written for the Linux kernel, touse and export block devices over a network (TCP) link. Its feature set wasvery limited, however, which limited its practical usability for manypurposes. Over the years, however, the protocol has evolved, with featuressuch as better negotiation, improved reliability through flush requests, andawareness of holes in backing files being implemented. Recent versions of QEMU implement the client side of the protocol, while atthe same time also being able to export local resources through NBD. Thissituation makes it possible for NBD to be used as a protocol for sharedstorage, backup, or mirroring of resources to other systems for livemigration. We will quickly cover the history of the protocol, describing some of thefeatures that were added over the years; make a short comparison againstsimilar protocols such as iSCSI and AoE and why NBD is relevant in thatcontext; and then move on to newer features that were added to the protocol atthe request of the QEMU developers.