Skip to content

Documentation: Add an explanation of NFSv4 client identifiers

Dave Wysochanski requested to merge dwysocha/centos-stream-9:guilt/bz2112933 into main

Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2112933
Upstream Status: linus.git Testing: Not applicable (docs only)

commit a28faaddb2be19659701602fc7c9934ff5fc3fa5
Author: Chuck Lever chuck.lever@oracle.com
Date: Mon Apr 18 11:58:50 2022 -0400

Documentation: Add an explanation of NFSv4 client identifiers  

To enable NFSv4 to work correctly, NFSv4 client identifiers have  
to be globally unique and persistent over client reboots. We  
believe that in many cases, a good default identifier can be  
chosen and set when a client system is imaged.  

Because there are many different ways a system can be imaged,  
provide an explanation of how NFSv4 client identifiers and  
principals can be set by install scripts and imaging tools.  

Additional cases, such as NFSv4 clients running in containers, also  
need unique and persistent identifiers. The Linux NFS community  
sets forth this explanation to aid those who create and manage  
container environments.  

Signed-off-by: Chuck Lever <chuck.lever@oracle.com>  
Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>

Signed-off-by: Dave Wysochanski dwysocha@redhat.com

Edited by Dave Wysochanski

Merge request reports