weizhouapache commented on pull request #4551: URL: https://github.com/apache/cloudstack/pull/4551#issuecomment-748005638
> @weizhouapache thanks for the pointers > > 1. The logic for cleaning up the volume on expiration of the download url is still as is, but this just removes any dangling volume entries left behind immediately after migration of volumes takes place just in case there exists any entries for that volume on the secondary store > 2. Since we are only clearing up what has been marked as destroyed / expunged, would it be necessary to enclose it within a global setting? @Pearl1594 thanks. sorry I did not test the storage migration. could you tell me what to do on old volume when it is copied to another pool ? Destroy or expunge it ? ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
