Libvirt: clean driver from libvirt calls
General idea behind this blueprint is to provide a layer between
driver.py and libvirt to split specifications and implementations.
This blueprint continue work already done in previous releases by
encapsulate host related libvirt calls in a Host's object and domain
related libvirt calls in a Guest's object.
Most of the code in libvirt.driver are already tested so we can expect
no regression and problably a better coverage since every new methods
introduced in Host and Guest will come with new tests.
Since several portions of code will be moved this will probably imply
more conflicts during a backport so I will be able to review/help any
of them.
Finally we can expect to reduce complexity of driver and help
maintainability
Blueprint information
- Status:
- Complete
- Approver:
- Matt Riedemann
- Priority:
- Low
- Drafter:
- Sahid Orentino
- Direction:
- Approved
- Assignee:
- Sahid Orentino
- Definition:
- Approved
- Series goal:
- Accepted for newton
- Implementation:
- Implemented
- Milestone target:
- newton-2
- Started by
- Sahid Orentino
- Completed by
- Matt Riedemann
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
libvirt: introduce freeze filesystems
Addressed by: https:/
libvirt: introduce thaw filesystems
Addressed by: https:/
libvirt: replace direct libvirt's call AbortJobBlock
Addressed by: https:/
libvirt: move find_disk to Guest's object
Addressed by: https:/
libvirt: introduce "snapshot" to Guest's object
Addressed by: https:/
libvirt: introduce block_stats to return device stats
Addressed by: https:/
libvirt: introduce "pause" to Guest's object
Addressed by: https:/
libvirt: wrapper list_instance_
Addressed by: https:/
libvirt: introduce "shutdown" to Guest's object
Addressed by: https:/
libvirt: introduce get_job_info to Guest's object
Addressed by: https:/
libvirt: configure migrate max downtime
Addressed by: https:/
libvirt: introduce "abort_job" to Guest's object
Addressed by: https:/
libvirt: introduce "migrate" to Guest's object
Discussed in IRC as a specless blueprint to track the cleanup work going on in the libvirt driver. -- mriedem 20151203
Addressed by: https:/
libvirt: check graphic/serial consoles at pre_live_migration step
Gerrit topic: https:/
Sorry, we have now hit the Non-Priority Feature Freeze for Mitaka. For more details please see: http://
--johnthetubaguy 2016.02.10
Addressed by: https:/
libvirt: live_migration_
Re-approved for newton given there were some outstanding changes still being made. In the future, we should probably target a blueprint per release and close it out when done, i.e. we should have closed this for mitaka and opened a new libvirt-
Addressed by: https:/
libvirt: remove live migrate workaround for an unsupported ver
Addressed by: https:/
libvirt: introduces object to handle domain xml migration
Addressed by: https:/
libvirt: split out code for detecting live migration job type
Addressed by: https:/
libvirt: split out code for determining if migration should abort
Addressed by: https:/
libvirt: split off code for updating live migration downtime
Addressed by: https:/
libvirt: split off code for updating migration stats in the DB
Addressed by: https:/
libvirt: split out code for processing migration tasks
Addressed by: https:/
libvirt: split out code for recovering after migration tasks
Gerrit topic: https:/
All of the current patches for this blueprint are merged, so I'm marking this as complete for Newton. We can create a libvirt-
Addressed by: https:/
Revert "libvirt: move graphic/serial consoles check to pre_live_migration"