100 likes | 182 Views
NFS Best Practices. beepy@netapp.com. The problem. Implementations arising Document best practices where choice exists Document behaviour where protocol spec is silent Moving drafts forward Pruning and bug fixing Way behind. Target is implementation table. Feature choices by implemention
E N D
NFS Best Practices beepy@netapp.com
The problem • Implementations arising • Document best practices where choice exists • Document behaviour where protocol spec is silent • Moving drafts forward • Pruning and bug fixing • Way behind
Target is implementation table • Feature choices by implemention • Sample tables to follow are incomplete • Need to work with implementers to document
Security • ACL description is complex - along lines of interpretation - Posix vs. NFS V4 • For Linux server, say, dependent on underlying OS
Delegations • Client has choices of behaviour on delegation • Ignore • Manage data, lock over wire • Close files, retain delegation
Named attributes • Behaviour is loosely defined in RFC
Magic numbers • # of operations, max size of COMPOUND request
Miscellaneous • ‘@sun.com’ domain attributed Ids, UID space considerations • Does client react to migration feedback • What minor versions (in future) supported
Terra incognita • What is not defined by protocol • Global name space • And more? • Any issues with moving from NFS Version 3 to NFS Version 4? • It depends on what the definition of “transparent” is…
Questions • Much more work here