qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Charles Kelimod <lichstor@gmail.com>
Cc: ronnie sahlberg <ronniesahlberg@gmail.com>,
	Paolo Bonzini <pbonzini@redhat.com>, Peter Lieven <pl@kamp.de>,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
	qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] iSER transport name is not good
Date: Fri, 8 Dec 2017 10:35:45 +0000	[thread overview]
Message-ID: <20171208103545.GE11767@redhat.com> (raw)
In-Reply-To: <CAO1xR-yCeF9NBBLL_fr7D3CoSq924r+kP_DA+vmg41acUF0Ehw@mail.gmail.com>

On Fri, Dec 08, 2017 at 03:27:27PM +0800, Charles Kelimod wrote:
> Hi Dave and Sahlberg,
> 
> for this type of name:iser://<host>/<iqn>/<lun>, I completely agree with
> you.
> my issue is when I create an vm from libvirt, the qemu command line should
> be:
> -drive
> file.driver=iser,file.portal=xx.xx.xx.xx:3260,file.target=iqn.xxx,file.lun=0,file.transport=iser
> 
> Actually "iser" is added by me in libvirt, which can work by a little
> modification. But I think file.transport=rdma would be better, as I think
> iser is protocol, and rdma is transport, and libvirt defined it, if I added
> a new transport name (iser) in libvirt, it will be confusable.

If libvirt already supports this, then we won't change it, as that just creates
needless backcompatibility problems. There's many cases where we have wierd or
undesirable names for things, but at a low level we just accept them and carry
on, as wierd names don't have any negative functional impact. At the higher
app user interface, it can be renamed as desired, since UI has no backcompat
problems, as long as the low level stays the same.


Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|

      parent reply	other threads:[~2017-12-08 10:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-07 13:08 [Qemu-devel] iSER transport name is not good Charles Kelimod
2017-12-07 18:41 ` Dr. David Alan Gilbert
2017-12-08  6:07   ` ronnie sahlberg
2017-12-08  7:27     ` Charles Kelimod
2017-12-08 10:30       ` Dr. David Alan Gilbert
2017-12-08 10:35       ` 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=20171208103545.GE11767@redhat.com \
    --to=berrange@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=lichstor@gmail.com \
    --cc=pbonzini@redhat.com \
    --cc=pl@kamp.de \
    --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 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).