atom feed89 messages in org.apache.incubator.cloudstack-devRe: Swift in 4.2 is broken, anybody w...
FromSent OnAttachments
Edison SuJul 3, 2013 2:29 pm 
Angeline ShenJul 3, 2013 2:56 pm 
Prasanna SanthanamJul 3, 2013 9:27 pm 
David NalleyJul 8, 2013 6:21 am 
Chip ChildersJul 8, 2013 6:39 am 
Chip ChildersJul 8, 2013 6:45 am 
Edison SuJul 8, 2013 10:13 am 
Edison SuJul 8, 2013 10:14 am 
Chip ChildersJul 8, 2013 10:24 am 
Sudha PonnagantiJul 8, 2013 10:30 am 
Chip ChildersJul 8, 2013 1:26 pm 
John BurwellJul 8, 2013 1:41 pm 
Chip ChildersJul 8, 2013 1:49 pm 
Animesh ChaturvediJul 8, 2013 3:11 pm 
Sudha PonnagantiJul 8, 2013 3:14 pm 
Edison SuJul 8, 2013 3:14 pm 
Angeline ShenJul 8, 2013 3:17 pm 
Edison SuJul 8, 2013 3:19 pm 
Sudha PonnagantiJul 8, 2013 3:23 pm 
Edison SuJul 8, 2013 3:29 pm 
Angeline ShenJul 8, 2013 4:04 pm 
Sudha PonnagantiJul 8, 2013 4:34 pm 
Edison SuJul 8, 2013 4:34 pm 
John BurwellJul 9, 2013 7:53 am 
Edison SuJul 9, 2013 10:56 am 
Chip ChildersJul 9, 2013 10:59 am 
Chip ChildersJul 9, 2013 11:00 am 
Edison SuJul 9, 2013 11:00 am 
Chip ChildersJul 9, 2013 11:08 am 
Edison SuJul 9, 2013 11:11 am 
Chip ChildersJul 9, 2013 11:21 am 
Edison SuJul 9, 2013 11:54 am 
Chip ChildersJul 9, 2013 11:56 am 
John BurwellJul 9, 2013 12:56 pm 
Sebastien GoasguenJul 9, 2013 1:06 pm 
Chip ChildersJul 9, 2013 1:09 pm 
53 later messages
Subject:Re: Swift in 4.2 is broken, anybody wants it to be supported in 4.2?
From:Chip Childers (chip@sungard.com)
Date:Jul 8, 2013 1:26:01 pm
List:org.apache.incubator.cloudstack-dev

On Mon, Jul 08, 2013 at 05:15:19PM +0000, Edison Su wrote:

-----Original Message----- From: Chip Childers [mailto:chip@sungard.com] Sent: Monday, July 08, 2013 6:46 AM To: <de@cloudstack.apache.org>; Edison Su Subject: Re: Swift in 4.2 is broken, anybody wants it to be supported in 4.2?

On Mon, Jul 8, 2013 at 9:22 AM, David Nalley <dav@gnsa.us> wrote:

On Wed, Jul 3, 2013 at 5:29 PM, Edison Su <Edis@citrix.com> wrote:

Due to object store refactor, Swift is broken. The reason, is that, we only have S3 test environment in our lab, so only S3 is tested for now. Before adding the feature back, I'd better ask from, the community, do

we want to support Swift? If so, which version of Swift? This will take some efforts to support Swift, are there any volunteers can help the integration?

Whats the bug ID for this? Unplanned/Unannounced deprecation of a feature is a blocker IMO. It engenders a bad relationship with our users, and strands them on previous versions with no good migration/upgrade path.

Edison, How broken is it? Is it shorter to fix or revert the object store changes?

It's not working at all. Not sure, revert object store will change it or not, as
this feature is not tested by QA for a long time.

So any idea what the effort of fixing it looks like? I mean, just because it wasn't tested in the last couple of releases doesn't necessarily mean that it wasn't working. As Sudha mentioned, it wasn't tested only because of a lack of change that triggered the expected need to perform regression testing of that feature.

I believe that this was an honest mistake, but we need to figure out what to do. I'm -1 on us saying "we'll drop Swift support". If necessary, I'd say that we need to roll back the object-store branch merge... I don't want to see that happen though. That's why I'm asking about effort to fix it.

-chip