Comment 6 for bug 1442193

Hello all,

This issue is associated with both tests behavior and product functionality. We are using the same test created for Swift for testing radosGW

However Swift, besides implementing the OpenStack Object Storage API v1, provides a bunch extensions like SLO/DLO (static/dynamic large objects), bulk operations (inc. server-side archive extraction), staticweb and many more.

Swift internally utilizes a pipeline-based architecture. Component delivering the base of OSOS API (the "proxy-server" WSGI application) could be seen as the last stage of such pipeline. Between it and user a lot of additional middleware modules exist and all of it are interconnected with the WSGI interface.

Based on all described above we able to say that:
for today we have a serious difference between Swift and Rados Gateway functionality.
reimplementing described above features for Rados Gateway could be “painful”.
maintaining this features in case if implemented would be another challenge.

From another side, even if we implement it, we will have another “big restrictions” - our configuration will be frozen and un-upgradeable, any additional third party extensions will not be available for Rados Gateway users.

Based on all of the above-mentioned, we are able to аllocate three main reasons for the falling tests:
issues in implementation of OpenStack Object Storage API v1 for Rados Gateway;
no similar extensions for Rados Gateway that exist for Swift;
in tempest tests for object storage present verification of functionality that did not described in official documentation for Swift API.

RefStack [1] can validate OpenStack Interoperability [2]. For Object store there is a short subset of basic Tempest tests that should be green.

Object Storage Capabilities objectstore-object-get✓ ✓objectstore-object-delete✓ ✓objectstore-object-copy✓ ✓objectstore-object-access✓ ✓objectstore-object-create✓ ✓objectstore-object-put✓ ✓objectstore-object-upload✓ ✓objectstore-object-versioned✓ ✓objectstore-temp-url-get✓ ✓

Based on all of the above-mentioned, we have agreed to add the release note about the issue and skip the unrequired tests

For more details related to executions of the tempest tests against Rados GW, please take a look into [3]

[1] https://wiki.openstack.org/wiki/RefStack
[2] http://www.openstack.org/brand/interop/
[3] http://cz7776.bud.mirantis.net:8080/jenkins/view/TEMPEST-9.0/