Re: [Libguestfs] v2v: -o rhv-upload - oVirt imageio random I/O APIs

On Wed, Mar 21, 2018 at 2:47 PM Richard W.M. Jones <rjones(a)redhat.com&gt; wrote: Yes, you can send the upload path /images/ticket-uuid or the special /images/* Both should behave in the same way. (2) We can make the OPTIONS request without needing to send an Authorization is always ignored, there is no need to send it to a server supporting options. Then you should use the special /images/* that does not require a ticket or an image. But not that trim will do nothing in the first version, and later it will be useful only for images on file storage, and some images on block storage (depending if the user selected wipe-after-delete). This is explain in the section about trim. Even when trim will be implemented for some image, it may not zero data. I hope that the semantics match what qemu-img/nbdkit expects? If we cannot implement a useful trim now, maybe we should not implement it at all, so virt-v2v cat tell that trim is not supported using OPTIONS? Nir