René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Improve volume migration without using secondary storage if possible","articleBody":"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. \r\n\r\n##### ISSUE TYPE\r\n\r\n * Improvement Request\r\n\r\n##### COMPONENT NAME\r\n\u003c!--\r\nCategorize the issue, e.g. API, VR, VPN, UI, etc.\r\n--\u003e\r\n~~~\r\nVolumes, migration\r\n~~~\r\n\r\n##### CLOUDSTACK VERSION\r\n\u003c!--\r\nNew line separated list of affected versions, commit ID for issues on master branch.\r\n--\u003e\r\n\r\n~~~\r\n4.9.x, 4.11.x, 4.13.x\r\n~~~","author":{"url":"https://github.com/yadvr","@type":"Person","name":"yadvr"},"datePublished":"2019-06-13T10:27:51.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":4},"url":"https://github.com/3404/cloudstack/issues/3404"}