All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Richard W.M. Jones" <rjones@redhat.com>
To: Nir Soffer <nirsof@gmail.com>
Cc: jcody@redhat.com, kwolf@redhat.com, qemu-block@nongnu.org,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	armbru@redhat.com, mreitz@redhat.com,
	"derez@redhat.com" <derez@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 1/2] block: curl: Allow arbitrary HTTP request headers to be set.
Date: Thu, 1 Mar 2018 15:46:03 +0000	[thread overview]
Message-ID: <20180301154603.GJ2787@redhat.com> (raw)
In-Reply-To: <CAMr-obsJtVe9h5CjQ1PkjBdrQhKBRP0RUAA2f3cQ7p_-2MG-EA@mail.gmail.com>

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

  reply	other threads:[~2018-03-01 15:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-01 13:58 [Qemu-devel] [PATCH 0/2] block: curl: Proof of concept for connecting to oVirt Richard W.M. Jones
2018-03-01 13:58 ` [Qemu-devel] [PATCH 1/2] block: curl: Allow arbitrary HTTP request headers to be set Richard W.M. Jones
2018-03-01 15:24   ` Nir Soffer
2018-03-01 15:46     ` Richard W.M. Jones [this message]
2018-03-01 16:11   ` Daniel P. Berrangé
2018-03-01 16:29     ` Richard W.M. Jones
2018-03-01 13:58 ` [Qemu-devel] [PATCH 2/2] block: curl: Allow Certificate Authority bundle to be passed in Richard W.M. Jones
2018-03-01 15:27   ` Nir Soffer
2018-03-01 15:34   ` Daniel P. Berrangé
2018-03-01 15:47     ` Richard W.M. Jones
2018-03-01 14:21 ` [Qemu-devel] [PATCH 0/2] block: curl: Proof of concept for connecting to oVirt no-reply
2018-03-01 14:31   ` Richard W.M. Jones
2018-03-01 14:49 ` no-reply
2018-03-01 15:38 ` no-reply
2018-03-01 16:54 ` no-reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180301154603.GJ2787@redhat.com \
    --to=rjones@redhat.com \
    --cc=armbru@redhat.com \
    --cc=derez@redhat.com \
    --cc=jcody@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=nirsof@gmail.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.