From: Wei Liu <wei.liu2@citrix.com>
To: "Luis R. Rodriguez" <mcgrof@kernel.org>
Cc: "Juergen Gross" <jgross@suse.com>,
"Charles Arndol" <carnold@suse.com>,
"Dave Scott" <Dave.Scott@citrix.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"Filipe Manco" <filipe.manco@neclab.eu>,
"Mike Latimer" <mlatimer@suse.com>,
"Anil Madhavapeddy" <anil@recoil.org>,
"Doug Goldstein" <cardoe@cardoe.com>,
"Jim Fehlig" <jfehlig@suse.com>,
"Jan Beulich" <JBeulich@suse.com>,
felipe.huici@neclab.eu, "Wei Liu" <wei.liu2@citrix.com>,
"Olaf Hering" <ohering@suse.de>,
"Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: 2016 Xen hackathon notes - xenstored
Date: Mon, 2 May 2016 12:32:50 +0100 [thread overview]
Message-ID: <20160502113250.GC26982@citrix.com> (raw)
In-Reply-To: <20160429185504.GO14141@wotan.suse.de>
Luis, thanks for starting this thread.
On Fri, Apr 29, 2016 at 08:55:04PM +0200, Luis R. Rodriguez wrote:
> On Fri, Apr 29, 2016 at 04:33:31PM +0200, Filipe Manco wrote:
> > Hi
> >
> > Regarding LiXS, our goal is to make it one of the upstream xenstore
> > alternatives. For that I already started getting internal approvals
> > to release the code open source, which should happen somewhere
> > around next month. I also need to fix some bugs and would like to do
> > some performance testing before the release.
> >
> > Once it is released, it would be nice to get some comments from the
> > community on the implementation, specifically about how to make it
> > upstreamable; I’ll let you know when the code is available.
> >
> > Does this plan sound reasonable?
>
> I have no say in the Xen community, but to me this sounds reasonable,
> you should have competing solutions and let people win, its the
> same principle that was applied to Linux Security Modules, for
> instance, and that philosophy tends to enable all viable options
> to compete while upstream. For Xen, there are already 2 xenstores,
> having another IMHO should just require commitment for a maintainer
> to upkeep it. Without that it should make no sense.
>
I think the best way forward is to post design doc and / or code to
xen-devel to decide what next step is. We shall discuss things based on
their merits.
> You also require C++ though ? That's a new requirement AFAICT, so
> that would need to be addressed.
>
IIRC we already need g++ to build QEMU (it doesn't get along with gcc
last time I checked), so that wouldn't be a big issue IMHO.
Wei.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
prev parent reply other threads:[~2016-05-02 11:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-28 18:34 2016 Xen hackathon notes - xenstored Luis R. Rodriguez
2016-04-29 13:19 ` Anil Madhavapeddy
2016-04-29 14:33 ` Filipe Manco
2016-04-29 18:55 ` Luis R. Rodriguez
2016-05-02 11:32 ` Wei Liu [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=20160502113250.GC26982@citrix.com \
--to=wei.liu2@citrix.com \
--cc=Dave.Scott@citrix.com \
--cc=JBeulich@suse.com \
--cc=anil@recoil.org \
--cc=cardoe@cardoe.com \
--cc=carnold@suse.com \
--cc=felipe.huici@neclab.eu \
--cc=filipe.manco@neclab.eu \
--cc=jfehlig@suse.com \
--cc=jgross@suse.com \
--cc=mcgrof@kernel.org \
--cc=mlatimer@suse.com \
--cc=ohering@suse.de \
--cc=roger.pau@citrix.com \
--cc=xen-devel@lists.xensource.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).