On Mon, 2009-01-05 at 10:40 -0600, Serge E. Hallyn wrote: > Quoting J. Bruce Fields (bfields@xxxxxxxxxxxx): > > Does anyone have any ideas about how the kernel's nfsd should interact > > (if at all) with network namespaces? > > > > I'm initially interested because I've been experimenting with modifying > > the server to allow it to present different exported filesystems > > depending on which ip address it's accessed through. One way to do that > > might be by modifying the kernel to behave as though there's a separate > > nfsd service per network namespace; then we'd need little or no > > modification of the userspace support daemons (statd, the portmapper, > > etc.)--just start multiple instances of them in separate network > > namespaces and teach the kernel to route requests to them to the > > corresponding loopback interface. (That would work at least for daemons > > that communicate with the kernel exclusively using rpc over loopback. > > We could perhaps do something similar with the various /proc and nfsctl > > interfaces.) This sounds good. It is somewhat related to UTS namespaces because the hostname reported from the UTS namespace and the DNS name might not match. I haven't thoroughly explored all the combinations but I suspect the use of network namespaces could play a part in that depending on what choices the administrator(s) make. > > I'm also curious more generally whether anyone's thought about how nfsd > > should behave in the presence of containers. I have only thought about how nfsd should see clients in different UTS and mount namespaces. The conclusion I came to was NFS should use whatever name was used with the original mount. So if we mounted an NFS export and then create a container that uses that mount then it should use the hostname of the original container. However if the child container then does another NFS mount then the child's hostname ought to be used for the new mount. > I suspect Eric has had more detailed thoughts than I so I'm waiting > to see his response. Matt sent a patchset to deal with sunrpc/nfs/uts > namespaces which I haven't yet had a chance to look at, so he might > also have some good comments at this point. Seems there's some confusion -- that patchset went out privately during the holidays. Now is a good time to repost it publicly though. I'll cc folks on this thread. I'm also planning on cc'ing nfs-devel to get their thoughts. Cheers, -Matt Helsley _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/containers