All of lore.kernel.org
 help / color / mirror / Atom feed
From: Doug Goldstein <cardoe@cardoe.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	Jim Fehlig <jfehlig@suse.com>
Cc: Ian Jackson <Ian.Jackson@eu.citrix.com>,
	xen-devel <xen-devel@lists.xen.org>,
	Wei Liu <wei.liu2@citrix.com>,
	Ian Campbell <Ian.Campbell@citrix.com>,
	Ken Johnson <ken@suse.com>
Subject: Re: [RFC] support more qdisk types
Date: Wed, 27 Jan 2016 14:25:51 -0600	[thread overview]
Message-ID: <56A927CF.2030708@cardoe.com> (raw)
In-Reply-To: <20160127183220.GC3134@char.us.oracle.com>


[-- Attachment #1.1: Type: text/plain, Size: 1715 bytes --]

On 1/27/16 12:32 PM, Konrad Rzeszutek Wilk wrote:
> On Mon, Jan 25, 2016 at 05:25:02PM -0700, Jim Fehlig wrote:
>> I would like to hear the community's opinion on supporting more qdisk types in
>> xl/libxl, e.g. nbd, rbd, iSCSI, etc. I prefer supporting additional qdisk types
>> in libxl over apps like xl or libvirt doing all the setup, producing a block
>> device, and then passing that to libxl. Each libxl app would have to
>> re-implement functionality already provided by qdisk. libxl already supports
>> IDE, AHCI, SCSI, and Xen PV qdisks. My suggestion is to extend that to initially
>> include nbd, rbd, and iSCSI. Sheepdog, ssh, etc. could be added in the future.
> 
> ssh?
>>
>> I considered several approaches to supporting additional qdisk types, based
>> primarily on changes to the disk cfg and interface. At one extreme is to change
>> nothing and use the existing 'target=' to encode all required config for the
>> additional qdisk types. libxl would need to be taught how to turn the blob into
>> an appropriate qdisk. At the other extreme is extending xl-disk-configuration
> 
> Either way - new backends would require changes in both libxl and libvirt right?
> The libxl would need to understand the new 'target=' blob to parse it out?
> 

libvirt would probably just do what its doing now. Since it can setup
the connection and pass the file descriptor into libxl. Honestly I don't
see the advantage here because libvirt does a better job from a security
standpoint and unless the goal is to have everything and the kitchen
sink in libxl/xl. There's already a number of ways to skin the cat (xl,
libvirt, xapi, openstack), why another one?

-- 
Doug Goldstein


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 959 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2016-01-27 20:25 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-26  0:25 [RFC] support more qdisk types Jim Fehlig
2016-01-27 18:32 ` Konrad Rzeszutek Wilk
2016-01-27 20:25   ` Doug Goldstein [this message]
2016-01-27 21:09     ` Konrad Rzeszutek Wilk
2016-01-28  2:42       ` Jim Fehlig
2016-01-29 14:07         ` Konrad Rzeszutek Wilk
2016-01-29 17:18           ` Jim Fehlig
2016-01-29 17:59             ` Konrad Rzeszutek Wilk
2016-01-28  2:37     ` Jim Fehlig
2016-01-29 14:21       ` Doug Goldstein
2016-01-28  2:27   ` Jim Fehlig
2016-02-02 14:59 ` Wei Liu
2016-02-02 22:06   ` Jim Fehlig
2016-02-03  9:56     ` Ian Campbell
2016-02-04  2:53       ` Jim Fehlig
2016-02-04 10:16         ` Ian Campbell
2016-02-09  0:54         ` Jim Fehlig
2016-02-09  9:35           ` Ian Campbell
2016-02-09 10:58           ` Ian Jackson
2016-02-03 10:35     ` Wei Liu
2016-02-03 10:51       ` Ian Campbell
2016-02-03 10:55         ` Wei Liu
2016-02-03 11:05           ` Ian Campbell
2016-02-03 11:08             ` Wei Liu
2016-02-03 11:15             ` Roger Pau Monné

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=56A927CF.2030708@cardoe.com \
    --to=cardoe@cardoe.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=jfehlig@suse.com \
    --cc=ken@suse.com \
    --cc=konrad.wilk@oracle.com \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xen.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.