Live Migration broken in Mitaka due to Nova Object Change
Bug #1551954 reported by
Drew Thorstensen
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nova-powervm |
Fix Released
|
Undecided
|
Kyle L. Henderson |
Bug Description
With the objectify-
This requires a per-virt driver object to be registered in the conductor. This change impacts PowerVM because the driver (being out of tree) can not register an object on the main nova conductor.
PowerVM needs to move to a migration object model. However, even upon doing so, since that object (being out of tree) can't be registered on the main conductor it is not clear how the PowerVM driver can perform a live migration.
To post a comment you must log in.
This was discussed in the following IRC chat: http:// eavesdrop. openstack. org/irclogs/ %23openstack- nova/%23opensta ck-nova. 2016-02- 24.log. html
See the discussion around 15:55