Improve XenAPI live block migration
Registered by
John Garbutt
The current live block migration doesn't work well with volumes are attached.
In particular we should look at iSCSI and NFS with XenSM.
Blueprint information
- Status:
- Complete
- Approver:
- Vish Ishaya
- Priority:
- Low
- Drafter:
- John Garbutt
- Direction:
- Approved
- Assignee:
- John Garbutt
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
-
Blocked
- Milestone target:
- None
- Started by
- John Garbutt
- Completed by
- John Garbutt
Related branches
Related bugs
Sprints
Whiteboard
Killing this off now, work is being done here:
https:/
----
Blocked on external dependency:
Need the appropriate changes to XCP/XenServer
-----
The current plan involves building a new SR to XenAPI.
This SR would use the volume id as the "content-id"
We then need to modify xapi to ensure it detects when identical content-ids are found, and deals with the detach/attach of the volume correctly during the migration.
We also need to look at Quantum and how the VIFs are created on the destination, and ensure that the VIF is correctly configured before the VM starts at the destination.
(?)
