Now I'm in a quandary? We are pushing out a new infrastructure with 6 hosts and a san next month. We have been working with xcp but decided to drop it because of vdi lock up issues. We tested power outages with our xcp host and iscsi san and weren't happy with the results i.e the locked vdi issue.
So we have moved over to Debian 6 with xen 4 and begun testing. We plan to have a crack at setting up clvm later in the week to test live migrations and our iscsi san. Then I get your email saying that vdi lockups have been addressed in XCP 1.0 and I'm wondering what the best way forward is? I know there's not a right answer but if anyone had any thoughts on what is the best path I would appreciate them. Thanks, Chris On Mon, Feb 14, 2011 at 5:27 PM, Jonathan Ludlam < [email protected]> wrote: > I think that's very unlikely at this stage. I don't think we've actually > got any IB hardware, so we'd have a job testing it. If you have the hardware > and the time to test it, it might be something that could go into the next > release though? > > Jon > > -----Original Message----- > From: [email protected] [mailto:[email protected]] > Sent: 14 February 2011 17:03 > To: Jonathan Ludlam; [email protected] > Subject: RE: [Xen-API] Release date for XCP 1.0 stable > > Any chance InfiniBand support could be added into XCP? At one point in > time, I heard IB support was going to be added in XCP 1.0, but I have not > heard anything about it since. > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Jonathan Ludlam > Sent: Monday, February 14, 2011 10:11 AM > To: [email protected] > Subject: Re: [Xen-API] Release date for XCP 1.0 stable > > Hi all, > > OK, the saga of the XCP-1.0 release continues...! > > Code-wise, things are pretty much fixed at this point. We don't expect to > be > doing much more unless anyone points out some real showstoppers. Many > things > have been fixed since the beta came out, including the issue with VDIs > being > locked when a host is hard-powered off, and a nasty kernel oops when using > the md driver. > > What's currently blocking the 1.0 release is that we're working hard on > getting the documentation/wiki sorted out, which has long needed an > overhaul. We're currently thinking that, if everything works out fine, the > 23-34th is the expected date for the release. > > There is an rc2 available here: > http://www.xen.org/files/XenCloud/Software/xcp-1.0-rc2 > (build number 40948) > > Don't ask about rc1 :-) > > If anyone wants to install the rc2 and give its tyres a kick, I'd be very > grateful, particularly if you found any nasty surprises. > > Thanks all for your patience, > > Jon > > > > On 11 Feb 2011, at 08:08, Christian Fischer wrote: > > > On Friday 11 February 2011 08:54:05 Vincent Hanquez wrote: > >> On 11/02/11 07:10, Christian Fischer wrote: > >>> On Thursday 10 February 2011 19:58:26 Lars Kurth wrote: > >>>> Hi, > >>>> I can't answer the question on the painless upgrade path, but we are > >>>> aiming for a release date in about two weeks. > >>> > >>> Two weeks? Week two of february is this week. Is this a typo? > >> > >> There's nothing that says two weeks in the february month. > >> it probably means 2 weeks from when the mail has been sent... > > > > Well, Mike has announced the release for the second week of february in > the > > first mail of this thread ten days ago. Of course, Lars means two weeks > from > > when the mail has been sent. > > > > Is there a pre release younger than build 38754? > > > > _______________________________________________ > > xen-api mailing list > > [email protected] > > http://lists.xensource.com/mailman/listinfo/xen-api > > > _______________________________________________ > xen-api mailing list > [email protected] > http://lists.xensource.com/mailman/listinfo/xen-api > > > > _______________________________________________ > xen-api mailing list > [email protected] > http://lists.xensource.com/mailman/listinfo/xen-api >
_______________________________________________ xen-api mailing list [email protected] http://lists.xensource.com/mailman/listinfo/xen-api
