Bug 1326857 - [RFE] Support live migration across datacenters with non-shared storage
Summary: [RFE] Support live migration across datacenters with non-shared storage
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: RFEs
Version: 4.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium with 1 vote
Target Milestone: ---
: ---
Assignee: Rob Young
QA Contact: Gil Klein
URL:
Whiteboard:
Depends On:
Blocks: 845679
TreeView+ depends on / blocked
 
Reported: 2016-04-13 14:50 UTC by Neal Gompa
Modified: 2018-05-27 13:32 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-05-27 13:32:25 UTC
oVirt Team: Storage
Embargoed:
tnisan: ovirt-future?
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?


Attachments (Terms of Use)

Description Neal Gompa 2016-04-13 14:50:22 UTC
Description of problem:
In oVirt, there does not appear to be a mechanism for moving virtual machines across data centers that use local storage, even if non-live migration is an option.

However, libvirt seems to expose this capability[1][2].

VMware's product has the capability, calling it "Storage vMotion" and supporting live migrations across heterogeneous storage types, disparate data centers and long distances, among other things[3].

It'd be very useful, especially as all-in-one setups go away in favor of hosted engine with 4.0.0 and in scenarios where it's not feasible to make shared storage fast enough to be useful for the workloads, but the HA property of live migration is still desired.

[1]: http://hgj.hu/live-migrating-a-virtual-machine-with-libvirt-without-a-shared-storage/

[2]: https://www.redhat.com/archives/libvirt-users/2013-June/msg00065.html

[3]: https://www.vmware.com/products/vsphere/features/vmotion

Comment 1 Doron Fediuck 2018-05-27 13:32:25 UTC
Closing old RFEs.
If relevant, please re-open and explain why.
As always- patches are welcomed!


Note You need to log in before you can comment on or make changes to this bug.