Dave.Scott at eu
Dec 22, 2011, 1:56 AM
Post #2 of 2
In XCP cross-pool migration definitely requires some extra storage magic, since storage can only be shared within a pool.
If you are using vanilla xen then the storage is more under your direct control. This is both good and bad: you have the ultimate in flexibility but you also have to do a lot of stuff yourself.
If your research is mostly on the storage datapath then I would recommend you write a tapdisk plugin (like the ones for .vhd support, mirroring etc) and test it by manually setting up a tapdisk device with "tap-ctl". If you would like to present it as "globally shared storage" to lots of hosts/ pools then you could probably write a storage plugin for XCP... As part of the cross pool migrate/ storage migrate I'm working on a version 2 of the XCP storage control interface. I'd like to publish an early draft of an API in the new year, your feedback would be welcome.
On Dec 22, 2011, at 3:03 AM, "Ruijin Zhou" <zhouruijin2010 [at] gmail> wrote:
> Hi, Dave,
> Thanks for your information.
> It seems that CrossPoolMigratioon is more like a storage management
> tool than virtual machine itself. Is this the reason you plan to
> implement it on XCP/Xenserver rather than Xen hypervisor?
> Right now, I need CrossPoolMigratioon function on Xen so that I can do
> some research on virtual storage. Is it doable on Xen hypervisor? Or I
> need some function/API from XCP/Xenserver?
> My plan is close to this link http://wiki.xen.org/wiki/CrossPoolMigrationv1.
> Do you have any suggestions?
> Thank you very much for helping me.
> With warm regards,
> University of Florida,
> Ruijin Zhou
> zhourj [at] ufl
> xen-api mailing list
> xen-api [at] lists
xen-api mailing list
xen-api [at] lists