> Hello developers, > > I've asked the question about the 16 bit Export ID last week and I've learned > many good things from the discussion. I'm currently working on a FSAL to > support our storage backend. That backend is supposed to host virtual > machine files and we'd like to create a single NFS Export for every virtual > machine. This will make the provisioning of those virtual machines > (orchestration seems to be the latest buzzword :-) easier, and we can also > use NFS-Ganesha for access control, IP based or username based for > example. > > Thus I expect the NFS-Ganesha server exposes many NFS exports, and those > would be used by a single host each. For such a solution, we'll also generate > the NFS-Ganesha configuration file. I'd like to know if there are any > restrictions on the Export ID besides the 16 bit value range? > > For example, the easiest solution to generate a NFS-Ganesha configuration > file will be to sort our exports by some criteria and then assign each export a > counter value as its Export ID. However if Exports are added or removed the > Export ID for an exported filesystem can change. Does the NFS client care, > which Export ID is used on the NFS server? Would it even notice (is that > Export ID used in the NFSv3 or NFSv4 protocol somewhere)?
The exportid is not meaningful to the client, however, since it is part of the handle, and the clients expect handles to be unchanging for a specific file, changing the exportid for a given client's VM file would definitely cause problems. Frank --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus ------------------------------------------------------------------------------ _______________________________________________ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
