On Sat, Dec 03, 2016 at 11:01:06PM -0500, Jon Stanley wrote:
Per the server SIG meeting last week, I've updated the requirements doc for the NFS role (https://docs.google.com/document/d/1jLyKsECdHdlKltmHGgf_-iOKj-hj4Qjbh5Zgm7a-...) to clean up the user stories, and the actual requirements.
I think that there's only one outstanding issue with this, and it relates to the UI for creating the underlying storage.
Are you planning to support krb5 exports?
Under Requirements: 1, what about netgroups or dns wildcards?
Note that nfsd supports exporting subdirectories of filesystems as well as entire filesystem, but that support is inherently problematic. So, anything we can do to discourage that is welcome.
Under "Things that we need to do: 1) c) i)", unmounting an unexported filesystem is trickier than you'd expect: even after unexport, there are still some bits of state that can hang around holding references, so the only completely reliable way to do this is by stopping the server first (and then restarting it after unount).
When unexporting, it might be nice to warn that clients need to have unmounted first. (For extra credit, a list of possibly active clients could also be useful, but we have only very incomplete information about that right now, so that's best left as future work.)
Nit: s/machine has it's/machine has its/.
On containers: container support for knfsd is incomplete, so you won't be able to run different knfsd's inside containers. (That could change some day.)
--b.