XenServer Migrations
The ability to move an instance to a new host. The source instance is torn down after the move is confirmed successful. This is not intended to be a live migration implementation as other functionality is dependent on this feature.
Blueprint information
- Status:
- Complete
- Approver:
- Rick Clark
- Priority:
- High
- Drafter:
- Paul Voccio
- Direction:
- Approved
- Assignee:
- Matt Dietz
- Definition:
- Approved
- Series goal:
- Accepted for cactus
- Implementation:
- Implemented
- Milestone target:
- None
- Started by
- Matt Dietz
- Completed by
- Thierry Carrez
Whiteboard
Tasks:
* Modify the API actions to accept resize and pass back appropriate status code
* Implement Compute API endpoint with scheduler migrate cast
* Implement Compute Manager migrate call
* Implement migration database model and all appropriate state changes
* XenServer Virt Driver implementation
* Rsyncing VHD from Host to Host
* SSH'ing into the host... :-( (can this be done another way?)
* Rsync COW from Host to Host
* Re-attaching existing VHD (part of restore functionality, which doesn't yet exist?)
Sequence:
Client->API: POST /action Body {'resize': { 'flavorId': # } }
API->Scheduler: cast {'migrate', source_host, flavor, inst_id}
API->Client: HTTP 202 Accepted
Scheduler-
DestCompute-
SourceCompute-
SourceCompute-
SourceHost-
SourceHost-
SourceCompute-
SourceCompute-
SourceHost-
SourceHost-
SourceCompute-
DestCompute-
DestCompute-
Updated because I realized the scheduler shouldn't know anything about the request being made
Work Items
Dependency tree
* Blueprints in grey have been implemented.