atom feed38 messages in org.apache.incubator.cloudstack-devRe: Drop OVM in 4.0?
FromSent OnAttachments
Edison SuOct 17, 2012 11:25 am 
Kelcey Damage (BBITS)Oct 17, 2012 11:27 am 
Frank ZhangOct 17, 2012 11:35 am 
Kelcey Damage (BBITS)Oct 17, 2012 11:37 am 
Edison SuOct 17, 2012 11:37 am 
Kelcey Damage (BBITS)Oct 17, 2012 11:39 am 
David NalleyOct 17, 2012 11:40 am 
Frank ZhangOct 17, 2012 11:47 am 
David NalleyOct 17, 2012 11:51 am 
Sudha PonnagantiOct 17, 2012 11:53 am 
Sudha PonnagantiOct 17, 2012 12:20 pm 
Will ChanOct 17, 2012 1:55 pm 
Kristoffer Sheather - Cloud CentralOct 17, 2012 2:40 pm 
Outback DingoOct 17, 2012 2:42 pm 
Caleb CallOct 17, 2012 3:01 pm 
Kelcey Damage (BBITS)Oct 17, 2012 3:06 pm 
Chiradeep VittalOct 17, 2012 4:50 pm 
David NalleyOct 17, 2012 4:54 pm 
Edison SuOct 17, 2012 4:55 pm 
Chiradeep VittalOct 17, 2012 4:58 pm 
Frank ZhangOct 17, 2012 6:59 pm 
Joe BrockmeierOct 17, 2012 7:30 pm 
Chip ChildersOct 18, 2012 7:11 am 
Will ChanOct 18, 2012 10:01 am 
John KinsellaOct 18, 2012 10:04 am 
Jessica TomechakOct 18, 2012 10:05 am 
Will ChanOct 18, 2012 10:29 am 
Kevin KlugeOct 18, 2012 11:10 am 
Joe BrockmeierOct 18, 2012 12:36 pm 
David NalleyOct 18, 2012 12:47 pm 
Marcus SorensenOct 18, 2012 12:53 pm 
Edison SuOct 18, 2012 1:53 pm 
Joe BrockmeierOct 18, 2012 2:15 pm 
Edison SuOct 18, 2012 2:59 pm 
Chip ChildersOct 18, 2012 3:04 pm 
Joe BrockmeierOct 18, 2012 4:06 pm 
Caleb CallOct 18, 2012 4:55 pm 
Sudha PonnagantiOct 18, 2012 5:43 pm 
Subject:Re: Drop OVM in 4.0?
From:Chip Childers (chip@sungard.com)
Date:Oct 18, 2012 7:11:11 am
List:org.apache.incubator.cloudstack-dev

On Wed, Oct 17, 2012 at 10:30 PM, Joe Brockmeier <jz@zonker.net> wrote:

On Wed, Oct 17, 2012 at 04:50:41PM -0700, Chiradeep Vittal wrote:

+1 on fixing in a 4.0.x. We need to make some tough decisions if we want "time based releases". We already dropped AutoScale and Brocade even though they were essentially code-complete for this reason. This is an issue that is of uncertain size (weeks at least) to fix. There is just too much uncertainty. Also it seems that folks want the latest version of OVM anyway, which would not be helped by fixing this in 4.0

We do need to make tough decisions for time-based releases, but we're not quite there yet.

IIRC one of the criteria for 4.0.0-incubating is that we'd support upgrades from prior releases of CloudStack[1] and AutoScale and Brocade were not in those releases - OVM was.

That certainly was the case, but we might need to rethink that assumption. There are really 2 issues: supporting the latest version of OVM and / or fixing the previous OVM support.

I understand the point about supporting the latest OVM version being "at least > 1 week". I haven't seen any answer to "fixing" the issues for the previously supported OVM version. Does anyone have a good handle on that effort? If it's equal or similar to making it work on the latest OVM, then perhaps we are talking about the same thing... If they are significantly different efforts, then we have to make a different decision.

It might be easier for folks to make a decision if we had a clear timeline for a 4.0.x release with OVM support and some idea who's going to be picking that up. (e.g., something like "Edison will be working on this feature and we're expecting it to be in master within two weeks of shipping 4.0.0-incubating).

Or at least a reasonable estimate for the different versions of "fixing" this problem (per my question above).

Holding the release up for an additional week (or longer) is not an attractive option, but neither is letting down a whole set of users who depend on OVM.

+1

[1]CloudStack - not CloudPlatform