Idea #6171
closed
[FUSE] Document the writable FUSE mount
Description
In an appropriate place in the user documentation, introduce the writable FUSE mount. Discuss how it can be used in jobs to make it easier to use legacy tools in Arvados. Document the limitations of the write support: which operations will succeed, and which will fail.
Related issues
Updated by Brett Smith over 9 years ago
- Project changed from 35 to Arvados
- Category set to FUSE
- Target version set to 2015-07-08 sprint
Updated by Brett Smith over 9 years ago
- Project changed from Arvados to 35
- Category deleted (
FUSE)
Updated by Brett Smith over 9 years ago
- Project changed from 35 to Arvados
- Release changed from 5 to 9
Updated by Peter Amstutz over 9 years ago
- Assigned To set to Peter Amstutz
I think this is already mostly done in #3198, what do you think?
Updated by Peter Amstutz over 9 years ago
- Status changed from New to In Progress
Updated by Brett Smith over 9 years ago
- Status changed from In Progress to Resolved
We are going to call the current documentation good enough, and close the ticket.
The main thing in the description that's not currently addressed is discussion about how to use the writable FUSE mount with your job. There's good reason for that: Crunch currently doesn't expose a writable mount to jobs, so there's no way to do that currently. We will add that documentation as part of the Crunch integration once we decide to do that.
Updated by Tom Clegg over 9 years ago
(time warp here)
Two distinct(?) doc stories here:- "limitations of write support" is probably what Peter means by "mostly done". It might be helpful to add some scenarios to illustrate the conditions in which writable fuse is a good/bad idea.
- "how to use writable FUSE to make your jobs faster and easier to write". This isn't purely a documentation story in that (AFAIK) we don't have a working example. Ideally we'll outfit Crunch to make the example really easy. In the meantime it might be feasible to run a writable mount from inside the job.