cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-9022) We should keep Destroyed volumes for some time
Date Thu, 03 Dec 2015 18:55:11 GMT

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

ASF subversion and git services commented on CLOUDSTACK-9022:
-------------------------------------------------------------

Commit f9775de8ffcd0c07bfd7e670819e0142663cfde1 in cloudstack's branch refs/heads/master from
[~dahn]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=f9775de ]

Merge release branch 4.6 to master

* 4.6:
  CLOUDSTACK-9022: move storage.cleanup related global configurations to StorageManager
  CLOUDSTACK-9022: keep Destroyed volumes for sometime

 Conflicts:
	server/src/com/cloud/storage/StorageManagerImpl.java


> We should keep Destroyed volumes for some time
> ----------------------------------------------
>
>                 Key: CLOUDSTACK-9022
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9022
>             Project: CloudStack
>          Issue Type: Improvement
>      Security Level: Public(Anyone can view this level - this is the default.) 
>            Reporter: Wei Zhou
>            Assignee: Wei Zhou
>
> for now, the Destroyed volumes will be expunged in Storage cleanup thread, no matter
when they are destroyed.
> In Expunging vm, we only clean the Destroyed vms which have been destroyed at least 'expunge.delay'
seconds.
> We need to add the similar configuration for volumes.



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

Mime
View raw message