On Tue, Oct 16, 2007 at 04:19:29PM +0100, Daniel P. Berrange wrote:
> Application users
> =================
>
> - virt-manager / virt-install
> - Enumerate available pools
> - Allocate volume from pool
> - Create guest with volume
When we support migration the storage API should let us do sanity
checking prior to migration. The metadata provided for a poool and
a volume should allow an algorithm sort of like this
For each disk assigned to the guest
- Lookup volume associated with the path on the source host
- Lookup volume associated with the path on the dest host
- If the dest volume is missing, refuse to migrate
- If the dest volume has as different UUID refuse to migrate
(Sync UUID to SCSI worldwide name perhaps ?)
- Lookup pool associated with the volume on source host
- Lookup pool associated with the volume on dest host
- If the pool is different, then refuse to migrate (catches
case of a different NFS mount being used, or it being a
local internal storage pool, for example)
Dan.
--
|=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=|
|=- Perl modules: http://search.cpan.org/~danberr/ -=|
|=- Projects: http://freshmeat.net/~danielpb/ -=|
|=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|
--
Libvir-list mailing list
Libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list