cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Animesh Chaturvedi (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CLOUDSTACK-3818) NFS Cache Improperly Named
Date Wed, 07 Aug 2013 18:47:39 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-3818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Animesh Chaturvedi updated CLOUDSTACK-3818:
-------------------------------------------


These blockers and critical issues are resolved but not verified. Reporters of these issues
please verify the fixes and help close these issues
                
> 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