From: Keir Fraser <keir.fraser@eu.citrix.com>
To: John Levon <levon@movementarian.org>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH] [Xend] Move some backend configuration
Date: Thu, 02 Oct 2008 16:25:39 +0100 [thread overview]
Message-ID: <C50AA683.27A6B%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <20081002150929.GC1088@totally.trollied.org.uk>
On 2/10/08 16:09, "John Levon" <levon@movementarian.org> wrote:
>> What happens if you try to write them, and fail? What are they actually used
>> for (e.g., communication with your own xvm tool stack?).
>
> They're both tool stack values, so in the sense that we can permanently
> patch xenstored, you don't need the change, you're right. Although, we're
> already
> carrying way way too much customizations.
Well, you don't need to patch xenstored. Your customised toolstack -- the
one that consumes these extra nodes -- can also open them up, right? The
only reason to open them in xend is if that is the difference between them
working and not working running against the default open-source toolstack.
I will allow these through if there is a net win for compatibility with the
default open-source toolstack. But I don't particularly want to do so just
to save you a one-line patch to your xend or equivalent.
> I don't see it going away, so in my mind explicitly saying now that you
> should only use guest/$(VENDOR) will avoid a lot of trouble down the
> line.
Mmm... I suppose I can see logic here. Vendor daemons running alongside
open-source xend for example.
-- Keir
next prev parent reply other threads:[~2008-10-02 15:25 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-30 14:24 [PATCH] [Xend] Move some backend configuration Pascal Bouchareine
2008-09-30 14:43 ` John Levon
2008-09-30 14:48 ` Keir Fraser
2008-09-30 14:58 ` John Levon
2008-09-30 15:09 ` Keir Fraser
2008-09-30 15:14 ` Ian Jackson
2008-09-30 15:30 ` Daniel P. Berrange
2008-09-30 16:09 ` Keir Fraser
2008-09-30 16:35 ` John Levon
2008-09-30 17:21 ` Pascal Bouchareine
2008-09-30 16:35 ` Daniel P. Berrange
2008-09-30 16:39 ` John Levon
2008-09-30 16:46 ` Keir Fraser
2008-09-30 17:08 ` Daniel P. Berrange
2008-09-30 17:09 ` Pascal Bouchareine
2008-10-02 9:34 ` Ian Jackson
2008-10-02 9:49 ` Keir Fraser
2008-10-02 10:16 ` Pascal Bouchareine
2008-10-02 10:20 ` Keir Fraser
2008-10-02 10:21 ` Ian Jackson
2008-10-02 10:28 ` Keir Fraser
2008-10-02 10:31 ` Ian Jackson
2008-10-02 13:45 ` John Levon
2008-10-02 14:04 ` Keir Fraser
2008-10-02 14:09 ` Keir Fraser
2008-10-02 15:09 ` John Levon
2008-10-02 15:25 ` Keir Fraser [this message]
2008-10-02 17:21 ` John Levon
2008-10-02 14:16 ` Ian Jackson
2008-09-30 15:11 ` Pascal Bouchareine
2008-09-30 15:02 ` Keir Fraser
2008-09-30 15:06 ` John Levon
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=C50AA683.27A6B%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=levon@movementarian.org \
--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 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.