XenAPI pool based migration should error when not shared storage

Bug #1026552 reported by John Garbutt
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Won't Fix
Wishlist
Unassigned

Bug Description

We should add a check to ensure the VM is on shared storage before trying to perform a pool migration.

See the TODO in virt/xenapi/vmops.py

Changed in nova:
assignee: nobody → John Garbutt (johngarbutt)
Thierry Carrez (ttx)
Changed in nova:
importance: Undecided → Low
status: New → Confirmed
Changed in nova:
assignee: John Garbutt (johngarbutt) → nobody
tags: added: xenserver
Revision history for this message
John Garbutt (johngarbutt) wrote :

Edge case for a very infrequently used feature.
The new block migration code path shows much more promise.

Changed in nova:
importance: Low → Wishlist
Revision history for this message
Bob Ball (bob-ball) wrote :

Agreed. What are the requirements for block migration path before we can deprecate the pool migration path?

Revision history for this message
John Garbutt (johngarbutt) wrote :

Once block migration works with attached shared storage (NFS and iSCSI) I think we are good.

Raise this one at the summit though, we should see what others think.

Revision history for this message
Tom Fifield (fifieldt) wrote :

This TODO still exists:

            self._ensure_host_in_aggregate(ctxt, src)
            # TODO(johngarbutt) we currently assume
            # instance is on a SR shared with other destination
            # block migration work will be able to resolve this

tags: added: live-migration
Bob Ball (bob-ball)
Changed in nova:
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.