From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Xen 4.3 development update CODE FREEZE HAS_BEGUN
Date: Thu, 18 Apr 2013 16:50:06 +0200 [thread overview]
Message-ID: <5170081E.9050405@citrix.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1304181230110.7254@kaball.uk.xensource.com>
On 18/04/13 13:30, Stefano Stabellini wrote:
> On Tue, 16 Apr 2013, George Dunlap wrote:
>> * Rationalized backend scripts
>> owner: roger@citrix
>> status: libxl hotplug sumbmitted. Protocol still needs to be finalized.
>> prognosis: Good
>
> OK
>
>> * Scripts for driver domains (depends on backend scripts)
>> owner: roger@citrix
>> status:
>> prognosis: Fair
>
> Are there going to make 4.3?
Regarding "Rationalized backend scripts", or what I usually call new
libxl hotplug interface, I think it could make it to 4.3. Here is a
small list about the pros/cons of taking that from my POV:
Cons:
- Touches generic device addition/removal code, and domain
creation/destruction.
- It introduces a new interface that is well defined and that we plan
to support, we have to be sure the interface is right.
Pros:
- All the code touched is exercised every time a domain/device is
created/destroyed, so the test system should be able to detect any
problems with that easily.
- Brings new functionality (iSCSI disks), which is not present in
libxl/xl, and should be considered a regression from xm.
- The new hotplug interface could be released as a tech preview,
guaranteeing us that we could still change it if we feel it doesn't
really suit our needs (I think it's best to have it as a tech preview
rather than not having it at all).
- The new iSCSI libxl/xl disk functionality could also be considered a
tech preview, again it's best to have it like that rather than not
having it at all, I've heard quite a lot of people asking about iSCSI
support in Xen.
next prev parent reply other threads:[~2013-04-18 14:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-16 12:22 Xen 4.3 development update CODE FREEZE HAS_BEGUN George Dunlap
2013-04-16 12:37 ` Ian Campbell
2013-04-16 12:39 ` George Dunlap
2013-04-16 12:50 ` George Dunlap
2013-04-16 15:02 ` Wei Liu
2013-04-16 15:20 ` George Dunlap
2013-04-16 16:11 ` Wei Liu
2013-04-16 16:24 ` George Dunlap
2013-04-18 18:09 ` Wei Liu
2013-04-19 7:50 ` Ian Campbell
2013-04-19 18:22 ` Wei Liu
2013-04-16 12:51 ` George Dunlap
2013-04-16 12:57 ` Jan Beulich
2013-04-16 13:00 ` George Dunlap
2013-04-16 13:16 ` Jan Beulich
2013-04-16 15:16 ` George Dunlap
2013-04-16 15:34 ` Anthony PERARD
2013-04-18 11:30 ` Stefano Stabellini
2013-04-18 14:50 ` Roger Pau Monné [this message]
2013-04-18 16:26 ` George Dunlap
2013-04-18 19:58 ` Alex Bligh
2013-04-19 8:07 ` 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=5170081E.9050405@citrix.com \
--to=roger.pau@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=stefano.stabellini@eu.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.