rhtyd opened a new issue #3404: Improve volume migration without using secondary storage if possible URL: https://github.com/apache/cloudstack/issues/3404 Currently, a volume migration from one primary storage to another primary storage pool happens via the secondary storage (or a caching storage pool if available). It's possible that both the primary storages are reachable from one-another and in which case the migration can happen directly. In case of VMware, (did not test but per tribal knowledge) a snapshot is taken then it is copied to secondary storage then copied the OVA down to new storage, then a volume is deployed from that template. The aim of the issue is to ask if future versions can have the volume migration improved. ##### ISSUE TYPE * Improvement Request ##### COMPONENT NAME <!-- Categorize the issue, e.g. API, VR, VPN, UI, etc. --> ~~~ Volumes, migration ~~~ ##### CLOUDSTACK VERSION <!-- New line separated list of affected versions, commit ID for issues on master branch. --> ~~~ 4.9.x, 4.11.x, 4.13.x ~~~
---------------------------------------------------------------- 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: us...@infra.apache.org With regards, Apache Git Services
