[QA] Add test to check that S3 API works out of the box

[Denis Klepikov]

Please add test to check that S3 API works out of the box.

HA+Ubuntu+Ceph for all, RBD, RadosGW
3 controllers, 2 compute+OSD

Test plan must include:

- creating user, sub-user, set permissions for users;
- authentification test using access_key and secret_key;
- creation buckets;
- uploading objects into bucket;
- downloading objects from bucket;
- creation folder into bucket;
- list of all buckets;
- list of the objects inside bucket;

Related bug: https://bugs.launchpad.net/fuel/6.0.x/+bug/1446704

[Nastya Urlapova (aurlapova)]

Moved to 7.0, was covered by manual acceptance in 6.1.

[Timur Nurlygayanov (tnurlygayanov)]

Sergii, we need to test this case in MOS 6.1 during the acceptance testing-

[Roman Rufanov (rrufanov)]

customer found on 6.1 Not urgent - but need fix.

[Vitaly Sedelnik (vsedelnik)]

This bug is about creating test plan to validate S3 API support. It's internal Mirantis QA entry, I don't understand how it could be customer-found. Setting to Incomplete for 6.1-updates and 7.0-updates and reassigning to Roman R - please explain the customer issue.

[Roman Rufanov (rrufanov)]

It is Customer found because customer are finding that S3 APIs do not work. They do not work since we do not test them. There are about 20 complains on this since Jan.

[Aleksey Zvyagintsev (azvyagintsev)]

Moving to all incoming milestones like confirmed. we should test it.

[Artem Roma (aroma-x)]

No updates for 7.0 and 6.1 milestones for more than 4 weeks. Hence marked as invalid

[Maksym Shalamov (mshalamov)]

In case of this task was created utility for testing CRUD operation on RGW and Swift.
https://github.com/mshalamov/s3b

[Maksym Shalamov (mshalamov)]

S3 API emulation in Swift does not support multi-part upload (this functionality is used for uploading huge objects into Swift storage). However we are able to cover those points using only* swiftclient for connection via Swift API. Huge objects support in Swift API is provided through DLO and SLO [1].

However we are able to deploy Swift3 Middleware [2] for OpenStack Swift, which should allowed access to OpenStack swift via the Amazon S3 API, but this middleware is not a part of MOS, so that it has never been tested.

[1] http://docs.openstack.org/developer/swift/overview_large_objects.html
[2] https://github.com/openstack/swift3

[Maksym Shalamov (mshalamov)]

Please note that when you trying to connect RGW with using S3 API you should get "AccessDenied". It happened because into ceph
configuration file which located on nodes with ceph(/etc/ceph/ceph.conf), absent parameter rgw_s3_auth_use_keystone = true.

So, to solve this issue you should perform two action:

1) on all nodes with ceph you should add parameter rgw_s3_auth_use_keystone = true;
2) on all nodes with ceph you should restart ceph osd
     $ initctl restart ceph-osd id={ceph-osd-id-number}

[Bug Checker Bot (esikachev-l)]

(This check performed automatically)
Please, make sure that bug description contains the following sections filled in with the appropriate data related to the bug you are describing:

actual result

version

expected result

steps to reproduce

For more detailed information on the contents of each of the listed sections see https://wiki.openstack.org/wiki/Fuel/How_to_contribute#Here_is_how_you_file_a_bug

[Maksym Shalamov (mshalamov)]

In addition to my previous comment please note that last action is incorrect:

2) on all controllers you should restart redosgw service
     $ /etc/init.d/radosgw restart

[Maksym Shalamov (mshalamov)]

Hello all,

Appropriate tests has been added.
Please take a look into [1].

Please note that before perform any tests from the [1] you should perform appropriate actions from [2]

[1]https://mirantis.testrail.com/index.php?/suites/view/1744&group_by=cases:section_id&group_id=23947&group_order=asc
[2]https://docs.google.com/document/d/1o4RFNuWHOUkFzB9FIZ5u8Q9Jx0O1cZQPmBnqw8sBFsE/edit#heading=h.cof84543wggz