Configure NFS version for Primary Storage

[wido]

ISSUE TYPE

• Improvement Request

COMPONENT NAME

NFS Primary Storage

CLOUDSTACK VERSION

ALL

CONFIGURATION

• Primary Storage
• NFS

OS / ENVIRONMENT

• Ubuntu / CentOS

SUMMARY

NFS Primary Storage mounts are handled by libvirt.

Currently libvirt defaults to NFS version 3 when mounting while it does support NFS version 4 if provided in the XML definition: https://libvirt.org/formatstorage.html#StoragePoolSource

  <source>
    <host name='localhost'/>
    <dir path='/var/lib/libvirt/images'/>
    <format type='nfs'/>
    <protocol ver='4'/>
  </source>

Maybe pass the argument 'nfsvers' to the URL provided to the Management Server and then pass this down to the Hypervisors which generate the XML for libvirt.

EXPECTED RESULTS

Primary Storage is mounted over NFS version 4

[DaanHoogland]

looks great, @wido . plan to put it behind a config option? or in the create primary call? (/me having the impertinence of marking it for 4.16)

[wido]

looks great, @wido . plan to put it behind a config option? or in the create primary call? (/me having the impertinence of marking it for 4.16)

See: https://cloudstack.apache.org/api/apidocs-4.14/apis/createStoragePool.html

We provide the URL in this form:

nfs://my-nfs-server/exports/ps01

We could change that URL by setting:

nfs://my-nfs-server/exports/ps01?nfsvers=4

[DaanHoogland]

does that mean that it can be upgraded to version 4 by updating the URL, appending the nfsvers argument? (url is no argument for updateStoragePool now: https://cloudstack.apache.org/api/apidocs-4.14/apis/updateStoragePool.html)
or is any other mech envisioned?

[wido]

does that mean that it can be upgraded to version 4 by updating the URL, appending the nfsvers argument? (url is no argument for updateStoragePool now: https://cloudstack.apache.org/api/apidocs-4.14/apis/updateStoragePool.html)
or is any other mech envisioned?

I don't think we can do and want to do this for existing primary storages. People could hack the DB and modify it if they really want to.

Otherwise we only support it when adding a new Primary Storage. We just need to parse the URL and store the nfs version in the DB and pass it all the way down to the XML we provide to libvirt.

[DaanHoogland]

copy

[nvazquez]

@wido @DaanHoogland there is a global setting to control the NFS version for secondary storage 'secstorage.nfs.version' perhaps it's easier to include a new global setting for primary storage and pass the version on the storage pool parameters down to the XML? cc @weizhouapache

[GabrielBrascher]

@nvazquez this could be an option indeed

[yadvr]

@GabrielBrascher @wido @nvazquez @sureshanaparti @davidjumani @shwstppr @Pearl1594 @DaanHoogland @weizhouapache - any update on this, who's assigned/working on this? Or should we change milestone? Thanks.