qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Richard W.M. Jones" <rjones@redhat.com>
To: jcody@redhat.com
Cc: kwolf@redhat.com, mreitz@redhat.com, armbru@redhat.com,
	eblake@redhat.com, qemu-block@nongnu.org, qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH 0/2] block: curl: Proof of concept for connecting to oVirt.
Date: Thu,  1 Mar 2018 13:58:54 +0000	[thread overview]
Message-ID: <20180301135856.22698-1-rjones@redhat.com> (raw)

This is a proof of concept patch which needs a bunch more testing.
I'm just posting it to get feedback.

It's almost possible to connect qemu to an oVirt / RHV server and
upload or download or otherwise modify disk images.  However the
curl driver is missing a couple of features to satisfy oVirt's
authentication requirements, and these features could be generally
useful for others too.

The patches: Allow arbitrary headers to be sent, so you can add the
oVirt authentication ticket as a special header.  And allow you to
specify a CA bundle, which is required for servers which do client
authentication.

The particular tricky areas are:

 - I have no idea if I'm doing lists right (first patch), although
   it appears to work.

 - I did not test the QAPI stuff, and I'm not even sure how to go
   about that.

 - There's no documentation, but there's no documentation for many
   other curl driver features either.

 - There are no tests, but similarly no tests for other curl features.

Rich.

             reply	other threads:[~2018-03-01 13:59 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-01 13:58 Richard W.M. Jones [this message]
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
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=20180301135856.22698-1-rjones@redhat.com \
    --to=rjones@redhat.com \
    --cc=armbru@redhat.com \
    --cc=eblake@redhat.com \
    --cc=jcody@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).