All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org,
	Peter Lieven <pl@kamp.de>, Pino Toscano <ptoscano@redhat.com>,
	Ronnie Sahlberg <ronniesahlberg@gmail.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	jtc@redhat.com
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH 0/2] Remove need for -iscsi argument
Date: Thu, 8 Dec 2016 13:15:51 +0000	[thread overview]
Message-ID: <20161208131551.GF26641@redhat.com> (raw)
In-Reply-To: <20161208131204.GB3891@noname.str.redhat.com>

On Thu, Dec 08, 2016 at 02:12:04PM +0100, Kevin Wolf wrote:
> Am 08.12.2016 um 13:41 hat Daniel P. Berrange geschrieben:
> > This small series removes the need for using the -iscsi argument
> > by directly supporting all the -iscsi options against the block
> > device config eg instead of
> > 
> > $QEMU \
> >   -object secret,id=sec0,data=123456 \
> >   -drive driver=iscsi,file=iscsi://catbus/iqn.fedora:kvm/2 \
> >   -iscsi initiator-name=fish,user=test,password-secret=sec0,timeout=234 
> > 
> > you can now do it all against -drive
> > 
> > $QEMU \
> >   -object secret,id=sec0,data=123456 \
> >   -drive driver=iscsi,file=iscsi://catbus/iqn.fedora:kvm/2,\
> >          initiator-name=fish,user=test,password-secret=sec0,timeout=234 
> > 
> > This fixes the problem that you cannot associate -drive instances
> > with -iscsi args reliably due to IQNs containing chracters that
> > QEMU forbids in QemuOpts ID strings.
> > 
> > Pino had previously sent a patch to do this for initiator-name
> > back in the 2.6 dev cycle
> > 
> >   https://lists.nongnu.org/archive/html/qemu-block/2016-04/msg00246.html
> > 
> > This series supports all the -iscsi option names, except for
> > 'password' which is intentionally left out as it is insecure
> > and replaced by 'password-secret'.
> 
> I actually do the same as part of my iscsi for blockdev-add series,
> which I guess I better should have sent as an RFC even if it's yet
> untested to save you the work...
> 
> As I do more on top of just converting -iscsi, I would prefer using my
> patches even if you posted yours first.

I don't mind, as long as this gets done for 2.9 and doesn't slip for
yet another release.

Regards,
Daniel
-- 
|: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org              -o-             http://virt-manager.org :|
|: http://entangle-photo.org       -o-    http://search.cpan.org/~danberr/ :|

      reply	other threads:[~2016-12-08 13:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-08 12:41 [Qemu-devel] [PATCH 0/2] Remove need for -iscsi argument Daniel P. Berrange
2016-12-08 12:41 ` [Qemu-devel] [PATCH 1/2] iscsi: reduce code duplication parsing -iscsi opts Daniel P. Berrange
2016-12-08 12:41 ` [Qemu-devel] [PATCH 2/2] iscsi: support most -iscsi opts against block dev opts Daniel P. Berrange
2016-12-08 13:12 ` [Qemu-devel] [Qemu-block] [PATCH 0/2] Remove need for -iscsi argument Kevin Wolf
2016-12-08 13:15   ` Daniel P. Berrange [this message]

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=20161208131551.GF26641@redhat.com \
    --to=berrange@redhat.com \
    --cc=jtc@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=pl@kamp.de \
    --cc=ptoscano@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=ronniesahlberg@gmail.com \
    /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.