[openstack-dev] [tc] persistently single-vendor projects

Ian Cordasco sigmavirus24 at gmail.com
Thu Aug 4 18:51:26 UTC 2016


-----Original Message-----
From: Fox, Kevin M <kevin.fox at pnnl.gov>
Reply: OpenStack Development Mailing List (not for usage questions) <openstack-dev at lists.openstack.org>
Date: August 4, 2016 at 13:40:53
To: OpenStack Development Mailing List (not for usage questions) <openstack-dev at lists.openstack.org>
Subject:  Re: [openstack-dev] [tc] persistently single-vendor projects

> Sorry, I was a bit unclear here. I meant the radosgw in particular. I've seen multiple  
> OpenStack projects fail to integrate with it.
> The most recent example I can think of is Trove can't do database backups to it as the namespacing  
> is slightly different in the older radosgw versions. (I think this is made more uniform  
> in Jewel, but I haven't tested it). I know tempurl's work slightly differently too so  
> may affect services that work with them.
> I don't think the differences are really intentional, more that there isn't an official  
> swift api spec and no cross testing is done because the OpenStack api test suite doesn't  
> run against radosgw as its not in the tent.

And yet there's nothing stopping the radosgw developers (who are apparently aiming for Swift compatibility) from running those tests themselves in their testing infrastructure. The tests are open source even if there's no written specification for the API.

Ian Cordasco

More information about the OpenStack-dev mailing list