cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ustcweizhou <>
Subject [GitHub] cloudstack pull request: [4.6.1] CLOUDSTACK-9022: keep Destroyed v...
Date Mon, 30 Nov 2015 19:47:23 GMT
GitHub user ustcweizhou opened a pull request:

    [4.6.1] CLOUDSTACK-9022: keep Destroyed volumes for sometime

    for now, the Destroyed volumes will be expunged in Storage cleanup thread, no matter when
they are destroyed.
    In Expunging vm thread, we expunge the Destroyed vms which have been destroyed at least
'expunge.delay' seconds. We add the similar configuration for volumes.
    same to #1029 , for 4.6

You can merge this pull request into a Git repository by running:

    $ git pull storage-cleanup-delay-4.6

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1145
commit 9077c9a5b47224b2d00978ff67e9af6957ec589b
Author: Wei Zhou <>
Date:   2015-11-03T16:04:55Z

    CLOUDSTACK-9022: keep Destroyed volumes for sometime

commit 4ed1e0d5f809d1bb2845b6e076d55eeb1ce3f0f4
Author: Wei Zhou <>
Date:   2015-11-04T08:27:32Z

    CLOUDSTACK-9022: move storage.cleanup related global configurations to StorageManager


If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message