On Thu, Mar 01, 2018 at 03:24:48PM +0000, Nir Soffer wrote: > Other issue that you need to consider is that you cannot > create images via the http. Images are created only via > engine API/UI.
We've got a separate bit of Python creating the image so I think we're ok here. > What ovirt-imageio give you is a way to > read and write data to existing image. The url you get is > mostly like an open file descriptor you can use with read() > and write(). OK. In fact in my experiment with oVirt 4.2 it *did* work without the Authorization header, but we believed that was a bug in oVirt, we didn't know it was designed to do that, thanks for clarifying it. In any case I'm pretty sure we do need ca.pem (second patch). > Note that you cannot access yet a chain of image via a url, since > ovirt generate a random url per image in a chain. For example, > if you have this chain: > > base-img <- top-image (top) I think we're OK for what virt-v2v is doing. Thanks, Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com libguestfs lets you edit virtual machines. Supports shell scripting, bindings from many languages. http://libguestfs.org