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 Fri, 29 Apr 2016 20:57:13 GMT


ASF GitHub Bot commented on CLOUDSTACK-9368:

Github user rafaelweingartner commented on a diff in the pull request:
    --- Diff: core/src/com/cloud/agent/api/storage/ ---
    @@ -0,0 +1,44 @@
    +// Licensed to the Apache Software Foundation (ASF) under one
    +// or more contributor license agreements.  See the NOTICE file
    +// distributed with this work for additional information
    +// regarding copyright ownership.  The ASF licenses this file
    +// to you under the Apache License, Version 2.0 (the
    +// "License"); you may not use this file except in compliance
    +// with the License.  You may obtain a copy of the License at
    +// Unless required by applicable law or agreed to in writing,
    +// software distributed under the License is distributed on an
    +// KIND, either express or implied.  See the License for the
    +// specific language governing permissions and limitations
    +// under the License.
    +public abstract class StorageNfsVersionCommand extends Command {
    +    protected StorageNfsVersionCommand(){
    --- End diff --
    are you using this constructor?

> 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