Re: [openstack-dev] [tc] Swift api compat. Was: supporting Go

2016-05-09 Thread Fox, Kevin M
Sent: Monday, May 09, 2016 1:53:06 AM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [tc] Swift api compat. Was: supporting Go Fox, Kevin M wrote: > I think part of the problem with the whole Swift situation is that it does > something most other OpenStack projects do

Re: [openstack-dev] [tc] Swift api compat. Was: supporting Go

2016-05-09 Thread Thierry Carrez
Fox, Kevin M wrote: I think part of the problem with the whole Swift situation is that it does something most other OpenStack projects don't do. Its both a control plane and a data plane. [...] Yes, it is certainly part of the Go rationale (I wouldn't say "problem"). Swift implementing a dat

Re: [openstack-dev] [tc] Swift api compat. Was: supporting Go

2016-05-05 Thread Fox, Kevin M
ncorrect. Its been mostly good enough sort of with a bunch of issues that have plagued us. Thanks, Kevin From: Pete Zaitcev [zait...@redhat.com] Sent: Thursday, May 05, 2016 9:38 AM To: Fox, Kevin M Cc: OpenStack Development Mailing List (not for usage questi

Re: [openstack-dev] [tc] Swift api compat. Was: supporting Go

2016-05-05 Thread Pete Zaitcev
On Wed, 4 May 2016 21:52:49 + "Fox, Kevin M" wrote: > Swift is in a strange place where the api is implemented in a way to > favor one particular vendor backend implementation. Sorry, but I disagree with the above assessement. There is no one particular vendor like that, because the only ven

Re: [openstack-dev] [tc] Swift api compat. Was: supporting Go

2016-05-04 Thread Fox, Kevin M
I think part of the problem with the whole Swift situation is that it does something most other OpenStack projects don't do. Its both a control plane and a data plane. For example, Cinder provides a unified api and provides plugins to allow vendors to plug in their particular special sauce in.