cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Burwell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-3818) NFS Cache Improperly Named
Date Fri, 26 Jul 2013 16:27:48 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-3818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13720929#comment-13720929
] 

John Burwell commented on CLOUDSTACK-3818:
------------------------------------------

Min,

Ideally, both.  However, given the short window, the priority is for all user visible elements
(e.g. API, UI, configuration files, documentation, etc).

If we do not have time address code, please open a task ticket to refactor the naming internally
for post-4.2.0 work.

Thanks,
-John
                
> NFS Cache Improperly Named
> --------------------------
>
>                 Key: CLOUDSTACK-3818
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3818
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Doc, Storage Controller
>    Affects Versions: 4.2.0
>            Reporter: John Burwell
>            Assignee: Min Chen
>            Priority: Blocker
>
> Per conversations on the mailing list, the term "NFS" is deceptive since it contains
non-volatile data.  As such, we agreed to rename it to "NFS Staging Area".  I would suggest
using the term "Staging Area" since we may implement other strategies in the future.  Regardless
of the final term selected, the phrase "cache" needs to be removed.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message