Re:PlentyFS: PoC read-only filesystem with random contents g...
by dredmorbius on Monday October 19, 2020 @02:12PM
(#24829097)
https://en.wikipedia.org/wiki/Network_block_device
If I'm understanding correctly, this still requires one instance with real (vs. virtual) storage on it? The advantage of PlentyFS is that it effectively requires no storage anywhere.
I didn't write PlentyFS, but was participating (mostly not helpfully) in Lars Wirzenius's thread on Mastodon.
My idea was to look at an HTTP or WebDAV solution using FUSE. The server would "create' the content (thinking along the line of HTTP honeypots), the FUSE module would present the filesystem-based access. There's an existing WebFS fuse modele, also a WebDAV one IIRC.
Unfortunately, HHTP doesn't offer directory presentation, making full filesystem semantics difficult.
I'm looking at other possible options as well, the concept is interesting.
Re:PlentyFS: PoC read-only filesystem with random contents g...
by baq on Monday October 19, 2020 @07:28AM
(#24825315)
ndb is also quite fun in that you can rate-limit easily, so you can check what happens with your app on slow storage. don't make it too slow, the Linux kernel doesn't like that and can hang completely.
As in this article, we also use this for testing.