Most of them areoutdated, but provide historical design context.
They arenotuser documentation and should not be treated as such.
Documentation is available here.
VDSM will allow NFS domains to be accessed with the 4th version of the NFS protocol
- Make needed change in Ovirt-Engine
- Make needed change in the GUIs
- Make needed changes in VDSM
Currently VDSM only supports NFS version 3. Once this change is introduced VDSM will enable if client and server both support NFSv4 for domains to be accessed this way. By default VDSM will let the NFS protocol decide what is the optimal version to use. In some cases the user might want to prevent VDSM from accessing the the server with version 4. In order to accommodate that a new optional parameter has been introduced to the type specific arg dictionary to allow specifying a version manually.
- NFS connection creation
see GUI mock-up in “Advanced NFS Options” wiki page at: Features/AdvancedNfsOptions#User Experience
How to use
This should not be specified under normal use and VDSM should be allowed to decide the appropriate values. The new connection specific argument is:
- version - Optional, integer - The NFS protocol version number used to contact the server’s NFS service. If the server does not support the requested version, the mount request fails. If this option is not specified, the client negotiates a suitable version with the server, trying version 4 first, version 3 second.
User work flows
The user should be able to set a value after being aptly warned.