From: Joshua West <jwest@brandeis.edu>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: Tom Rotenberg <tom.rotenberg@gmail.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: When is the next version of xen is supposed to be released?
Date: Thu, 15 Oct 2009 12:06:34 -0400 [thread overview]
Message-ID: <4AD7488A.9050000@brandeis.edu> (raw)
In-Reply-To: <C6FD05DA.178BF%keir.fraser@eu.citrix.com>
Keir Fraser wrote:
> On 15/10/2009 16:51, "Joshua West" <jwest@brandeis.edu> wrote:
>
>
>> Can you elaborate on the HA solution? Will this be something like
>> Kemari, included with Xen, or something completely new?
>>
>
> Kemari or Remus.
>
Awesome -- both good projects.
>> Lastly, m/any changes to the XML-RPC Xen API?
>>
>
> I doubt it. Is anyone seriously working on that any more?
>
The API is pretty complete, so beyond simple extensions or bug fixes, I
wouldn't think anybody would even need to. Either way though, just as
long as it doesn't change (much), I'll stay happy as I've been working
quite a bit with it :-)
One other question -- any thoughts on when 3.4.2 will be released?
Thanks for the info on what we may see in the next version.
--
Joshua West
Senior Systems Engineer
Brandeis University
http://www.brandeis.edu
next prev parent reply other threads:[~2009-10-15 16:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-15 10:40 When is the next version of xen is supposed to be released? Tom Rotenberg
2009-10-15 11:25 ` Keir Fraser
2009-10-15 12:23 ` Pasi Kärkkäinen
2009-10-15 13:25 ` Keir Fraser
2009-10-15 15:51 ` Joshua West
2009-10-15 16:01 ` Keir Fraser
2009-10-15 16:06 ` Joshua West [this message]
2009-10-15 16:14 ` Keir Fraser
2009-10-15 17:38 ` [PATCH] pv bootloader support for bzip2/lzma compressed kernels for Xen 3.4.2 Pasi Kärkkäinen
2009-10-15 18:11 ` Keir Fraser
2009-10-15 18:17 ` Pasi Kärkkäinen
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=4AD7488A.9050000@brandeis.edu \
--to=jwest@brandeis.edu \
--cc=keir.fraser@eu.citrix.com \
--cc=tom.rotenberg@gmail.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.