Mess in live-migration compute-manager and drivers code
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Opinion
|
Wishlist
|
Timofey Durakov |
Bug Description
There is _live_migration
:param block_migration: if true, it was a block migration
:param migrate_data: implementation specific data
The problem is that current compute's manager code is libvirt-specific.
It operates values in migrate_data dictionary that valid only for libvirt driver implementation.
This doesn't cause any bug yet because other drivers doesn't implement cleanup method at all.
When anyone decide to implement this live-migration starts to fail. There is no valid ci job to verify that.
live_migration_
Changed in nova: | |
status: | New → In Progress |
Changed in nova: | |
importance: | Undecided → Low |
tags: | added: low-hanging-fruit |
tags: |
added: live-migrate removed: live-migration |
tags: |
added: live-migration removed: live-migrate |
Fix proposed to branch: master /review. openstack. org/216329
Review: https:/