Re: [Xen-cim] FYI - 3.0.3 code freeze & Xen CIM API

[Ewan Mellor <ewan@xxxxxxxxxxxxx>]

On Tue, Aug 22, 2006 at 10:15:31AM -0700, Gareth S Bestor wrote:

> In case some folks are not following xen-devel, 3.0.3 is now frozen.
> 
> >...The xend lifecycle management patches will be
> >held-over to the next release so it can become part of a larger set of
> >control tool changes.
> 
> With 3.0.3 frozen, I expect Ewan's new xend C API will be showing up in
> xen-unstable shortly. After some discussions over the past couple of weeks
> the decision was made for the Xen CIM API that for the immediate future we
> should proceed with replacing the current libxm/libvirt 'shim' in the CIM
> provider code today with direct calls to the new xend C API, as defined by
> Ewan. Please note, this DOES NOT preclude porting the providers to a
> proper full libvirt API at some point, but because of the immediate
> additional development work this will require - i.e.  replace the shim
> with libvirt PLUS add a new backend to libvirt for the new xend API - that
> this will not be our immediate focus. Since Ewan's new xend C API will
> only show up in 3.0.4, backward compatibility to 3.0.3 for the CIM
> providers will be handled by making the new xend compatible with a Xen
> 3.0.3 base (right Ewan?)

Yes, that's right.  We'll make sure that the Xend from the 3.0.4 release runs
on top of RHEL 5 / FC6, which we expect to be based on Xen 3.0.3.  The reason
for doing this is to make sure that we have a good story for the management
stack for RHEL 5, which of course could be around in the enterprise for a very
long time yet.  

SLES10 SP1 is targeted to work with Xen 3.0.4, so compatibility with SLES10 is
assured.

Please note that Xen 3.0.3 is in feature-freeze inside xen-unstable, but it's
not yet been forked.  The API work won't drop into xen-unstable until 3.0.3 is
forked to become the new xen-3.0-testing tree (a small number of weeks,
hopefully) and xen-unstable is unlocked again.

Ewan.

> Date: Tue, 22 Aug 2006 17:03:27 +0100
> From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
> Subject: [Xen-devel] 3.0.3 freeze
> To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
> Message-ID:
> <A95E2296287EAD4EB592B5DEEFCE0E9D5724D7@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
> Content-Type: text/plain; charset="us-ascii"
> 
> Folks,
> 
> I think its time to declare a 3.0.3 feature freeze. We've got all the
> 'must have' feature patches in -unstable and many of the 'would be nice'
> variety too.
> 
> Just to summarize, we have: the new scheduler, blktap with file-based VM
> storage, upgraded device emulation, new shadow pagetable code, PV
> drivers for HVM guests, networking support for segmentation offload,
> support for the Power architecture, misc performance optimizations and
> bug fixes.
> 
> There were a number of patches that haven't quite made the cut off due
> to various outstanding issues or lack of review time: The NUMA allocator
> patch has been observed to cause problems on at least one system. The PV
> framebuffer could do with a few interface tweaks and a code cleanup. The
> kexec/kdump patch just needs more testing [I feel bad about this one --
> maybe we can retrofit it]. The xend lifecycle management patches will be
> held-over to the next release so it can become part of a larger set of
> control tool changes.
> 
> Now the tree is in 'freeze' state, please can everyone get ready to do
> some serious testing. We're still working on a handful of known issues
> we can reproduce, so this message isn't quite a full call to arms for
> testing from the user community yet, but it would be great if developers
> could start giving it a workout.
> 
> Thanks,
> Ian

> _______________________________________________
> Xen-cim mailing list
> Xen-cim@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-cim


_______________________________________________
Xen-cim mailing list
Xen-cim@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-cim