From: Jim Fehlig <jfehlig@novell.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: LibVir <libvir-list@redhat.com>,
xen-devel <xen-devel@lists.xensource.com>,
"Daniel P. Berrange" <berrange@redhat.com>,
Gianni Tedesco <gianni.tedesco@citrix.com>
Subject: Re: Re: [libvirt] [RFC] libxenlight driver
Date: Fri, 21 Jan 2011 10:02:07 -0700 [thread overview]
Message-ID: <4D39BC0F.8030603@novell.com> (raw)
In-Reply-To: <1295629077.14780.403.camel@zakaz.uk.xensource.com>
Ian Campbell wrote:
> On Fri, 2011-01-21 at 16:44 +0000, Daniel P. Berrange wrote:
>
>> On a related note, where does XenAPI fit into this picture ?
>> Previously XenD would provide (at least some of) the XenAPI
>> functionality in the open source stack, while I understand
>> that the XenEnterprise had a separate impl of XenAPI. It
>> sounds like XenAPI is likely only relevant for XenEnterprise
>> connectivity in the future.
>>
>
> The xapi toolstack which implements XenAPI is now open source as well
> and is used in XCP (as well as XenServer).
>
But there is no intent on putting this toolstack in the traditional Xen
releases from xen.org correct?
Jim
next prev parent reply other threads:[~2011-01-21 17:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4D38CA05.2070601@novell.com>
[not found] ` <20110121111343.GE11539@redhat.com>
2011-01-21 15:48 ` [libvirt] [RFC] libxenlight driver Jim Fehlig
2011-01-21 16:33 ` Gianni Tedesco
2011-01-21 16:44 ` Daniel P. Berrange
2011-01-21 16:57 ` Ian Campbell
2011-01-21 17:02 ` Jim Fehlig [this message]
2011-01-21 17:09 ` Ian Campbell
2011-01-21 17:46 ` Ian Jackson
2011-01-21 17:01 ` Stefano Stabellini
2011-01-21 17:19 ` Gianni Tedesco
2011-01-21 16:54 ` Stefano Stabellini
2011-01-21 17:49 ` Ian Jackson
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=4D39BC0F.8030603@novell.com \
--to=jfehlig@novell.com \
--cc=Ian.Campbell@citrix.com \
--cc=berrange@redhat.com \
--cc=gianni.tedesco@citrix.com \
--cc=libvir-list@redhat.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 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.