And my mail client sent this before I'd written the last line which is "Any comments are welcome!"
Thanks, Dave > -----Original Message----- > From: [email protected] [mailto:xen-api- > [email protected]] On Behalf Of Dave Scott > Sent: 13 July 2011 15:22 > To: [email protected] > Subject: [Xen-API] cross-pool migrate, with any kind of storage (shared > or local) > > Hi, > > I've created a page on the wiki describing a new migration protocol for > xapi. The plan is to make migrate work both within a pool and across > pools, and to work with and without storage i.e. transparently migrate > storage if necessary. > > The page is here: > > http://wiki.xensource.com/xenwiki/CrossPoolMigration > > The rough idea is to: > 1. use an iSCSI target to export disks from the receiver to the > transmitter > 2. use tapdisk's log dirty mode to build a continuous disk copy program > -- perhaps we should go the full way and use the tapdisk block mirror > code to establish a full storage mirror? > 3. use the VM metadata export/import to move the VM metadata between > pools > > I'd also like to > * make the migration code unit-testable (so I can test the failure > paths easily) > * make the code more robust to host failures by host heartbeating > * make migrate properly cancellable > > I've started making a prototype-- so far I've written a simple python > wrapper around the iscsi target daemon: > > https://github.com/djs55/iscsi-target-manager > > _______________________________________________ > xen-api mailing list > [email protected] > http://lists.xensource.com/mailman/listinfo/xen-api _______________________________________________ xen-api mailing list [email protected] http://lists.xensource.com/mailman/listinfo/xen-api
