[
https://issues.apache.org/jira/browse/CLOUDSTACK-9022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15038314#comment-15038314
]
ASF subversion and git services commented on CLOUDSTACK-9022:
-------------------------------------------------------------
Commit 3b511a139d31301e44028169d6b7bfeca08093d6 in cloudstack's branch
refs/heads/master from [~remibergsma]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=3b511a1 ]
Merge pull request #1155 from DaanHoogland/merge-4.6
Merge 4.6there is one (simple) conflict so for formailty's sake I make this a
pull request.
@utscweizhou en @remibergsma please have a look/test-run
* pr/1155:
CLOUDSTACK-9022: move storage.cleanup related global configurations to
StorageManager
CLOUDSTACK-9022: keep Destroyed volumes for sometime
Signed-off-by: Remi Bergsma <[email protected]>
> 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)
