cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-9368) Fix for Support configurable NFS version for Secondary Storage mounts
Date Tue, 10 May 2016 11:23:12 GMT


ASF GitHub Bot commented on CLOUDSTACK-9368:

Github user koushik-das commented on the pull request:
    Looks like nfs version is only supported for VMware. If XS or KVM clusters are added to
the zone (having nfs version set on image store) will there be any side effects?
    What if this property is set on a image store which is not NFS?
    @sateesh-chodapuneedi can you review the VMware code?

> Fix for Support configurable NFS version for Secondary Storage mounts
> ---------------------------------------------------------------------
>                 Key: CLOUDSTACK-9368
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: VMware
>    Affects Versions: 4.9.0
>            Reporter: Nicolas Vazquez
>             Fix For: 4.9.0
> This issue address a problem introduced in [CLOUDSTACK-9252|]
in which NFS version couldn't be changed after hosts resources were configured on startup
(for hosts using `VmwareResource`), and as host parameters didn't include `nfs.version` key,
it was set `null`.
> h4. Proposed solution
> In this proposed solution `nfsVersion` would be passed in `NfsTO` through `CopyCommand`
to `VmwareResource`, who will check if NFS version is still configured or not. If not, it
will use the one sent in the command and will set it to its storage processor and storage
handler. After those setups, it will proceed executing command.

This message was sent by Atlassian JIRA

View raw message