On Thursday, 10 February 2011 at 12:40, Ian Campbell wrote:
> (cutting CC to just xen-devel)
>
> On Thu, 2011-02-10 at 11:31 +0000, Ian Campbell wrote:
> > On Wed, 2011-02-09 at 23:16 +0000, Brendan Cully wrote:
> > > I'd like to keep the fast resume option, and expect that it can be
> > > contained entirely in Xen-specific code. I'll try to get someone to
> > > look into it here.
>
> On that note: Is there someone around who is willing to more actively
> and visibly maintain Remus? i.e. make it work with the new toolstack,
> upstream it to the mainline kernel, work to get it into a state where it
> can be tested as a matter of course, and generally be seen to be
> improving it (and its integration/interaction with the rest of the
> ecosystem) with time?
>
> At the moment the impression is that Remus is mostly being left to rot
> apart from when noise gets made about specific issues.
I'd like to introduce Shriram Rajagopalan, another PhD student here at
UBC who has been doing a lot of work with Remus internally. Up to this
point he's concentrated on new features that aren't quite ready for
upstream yet: checkpoint compression, DRBD integration, and failback
(live resync back to the primary after it has recovered from
failure).
He's also started doing maintenance work for his own purposes that
would be beneficial for Xen: building a regression test suite, working
on pvops support, and planning xl integration. He's excited to take on
a maintenance role, and ready to put together a plan for upstreaming
his work.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home