[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-API] VDI import/export with deltas
> http://wiki.xensource.com/wiki/Disk_import/export_APIs This is great, but I think we're missing the ability to pull a VHD in or push a VHD out. The OpenStack case needs to call a vm-import giving a URL to pull a VHD from, and a vm-export to push a VHD out to. In particular I think we need to set specific headers as well, as authentication, so I'd like to propose the following as a hopefully simple extension: xe vdi-export uuid=$VDI format=vhd dest=http://192.168.0.1:5000/... headers:arbitrary_string=$AUTH_TOKEN xe vdi-import uuid=$RESTORE format=vhd source=http://192.168.0.1:5000/... headers:arbitrary_string=$AUTH_TOKEN OpenStack also has a case for using bittorrent to download the VDI from peers rather than the central server, but I don't see how to accomplish that with the current proposal without requiring double the disk space as we'd need to download it then push it into XS. Thoughts? Thanks, Bob > There's still time before 2.0 to change how these work, so your comments > and criticism would be appreciated. > > Thanks! > Dave > > [1] https://github.com/xapi-project/xapi-project/issues/1 > [2] https://github.com/xapi-project/xen-api/issues/1778 > [3] https://github.com/xapi-project/vhd-tool/pull/14 > _______________________________________________ > Xen-api mailing list > Xen-api@xxxxxxxxxxxxx > http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api _______________________________________________ Xen-api mailing list Xen-api@xxxxxxxxxxxxx http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |