Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Mon, 16 Mar 2015 03:43:56 +0000 (UTC)
From: "Rajani Karuturi (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12760115.1418040868000.100679.1426477436312@Atlassian.JIRA>
In-Reply-To: <JIRA.12760115.1418040868000@Atlassian.JIRA>
References: <JIRA.12760115.1418040868000@Atlassian.JIRA>
 <JIRA.12760115.1418040868179@arcas>
Subject: [jira] [Updated] (CLOUDSTACK-8045) Renaming "Volume Snapshots" to
 "Volume Backups."
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Rajani Karuturi updated CLOUDSTACK-8045:
----------------------------------------
    Fix Version/s:     (was: 4.5.0)
                   4.5.1

> Renaming "Volume Snapshots" to "Volume Backups."
> ------------------------------------------------
>
>                 Key: CLOUDSTACK-8045
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8045
>             Project: CloudStack
>          Issue Type: Improvement
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Snapshot, Volumes
>    Affects Versions: 4.3.1
>         Environment: NA
>            Reporter: Andrija Panic
>              Labels: snapshot, volumes
>             Fix For: 4.5.1
>
>
> There was a mailing thread long time ago = to acutally rename Volume Snapshot -  to Volume Backup or similar - snapshots are being copied over to Secondary storage as backup of the Volumes - so there is NO good reason to call this snapshot, since we can't really do anything with them in terms of easy restore etc - so I guess this would be really the logic step to rename it.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)