New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
jewel: rgw: improve support for Swift's object versioning. #10710
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The backport has been tested with the same subset of tests and version of Tempest like the source PR. Results:
|
ghost
changed the title
jewel, rgw: improve support for Swift's object versioning.
jewel: rgw: improve support for Swift's object versioning.
Aug 15, 2016
@rzarzynski could you please update the commit message to explain how the conflicts were resolved ? commit=c884a5c ; picked_from=$(git show --no-patch --pretty=%b $commit | perl -ne 'print if(s/.*cherry pick.* from commit (\w+).*/$1/)') ; diff -u --ignore-matching-lines '^[^+-]' <(git show $picked_from) <(git show $commit) --- /dev/fd/63 2016-08-15 23:40:57.190765188 +0200 +++ /dev/fd/62 2016-08-15 23:40:57.294765048 +0200 @@ -85,13 +90,11 @@ + } + op_ret = store->create_bucket(*(s->user), s->bucket, zonegroup_id, -- placement_rule, swift_ver_location, -- pquota_info, attrs, +- placement_rule, swift_ver_location, attrs, - info, pobjv, &ep_objv, creation_time, - pmaster_bucket, true); + placement_rule, s->bucket_info.swift_ver_location, -+ pquota_info, attrs, -+ info, pobjv, &ep_objv, creation_time, ++ attrs, info, pobjv, &ep_objv, creation_time, + pmaster_bucket, true); /* continue if EEXIST and create_bucket will fail below. this way we can * recover from a partial create by retrying it. */ @@ -106,10 +109,11 @@ + s->bucket_info.swift_versioning = (! swift_ver_location->empty()); + } + - /* This will also set the quota on the bucket. */ ++ /* This will also set the quota on the bucket. */ op_ret = rgw_bucket_set_attrs(store, s->bucket_info, attrs, &s->bucket_info.objv_tracker); -@@ -2511,6 +2524,18 @@ void RGWPutObj::execute() + } while (op_ret == -ECANCELED && tries++ < 20); +@@ -2414,6 +2428,18 @@ void RGWPutObj::execute() processor = select_processor(*static_cast(s->obj_ctx), &multipart); @@ -591,11 +595,10 @@ // vim: ts=8 sw=2 smarttab +#include -+ - #include "include/assert.h" + #include - #include "common/Formatter.h" -@@ -538,6 +540,33 @@ static void get_rmattrs_from_headers(const req_state * const s, + #include "include/assert.h" +@@ -507,6 +508,33 @@ static void get_rmattrs_from_headers(const req_state * const s, } } |
This patch allows RadosGW to pass the RefStack with an accuracy to the RFC7230 violation issue which is clearly a Tempest bug. Fixes: http://tracker.ceph.com/issues/15925 Signed-off-by: Radoslaw Zarzynski <rzarzynski@mirantis.com> (cherry picked from commit 237ad12) Conflicts: src/rgw/rgw_op.cc In contrast to master, Jewel doesn't support container quota of Swift API. All tracks of this feature have been eradicated from the patch. src/rgw/rgw_rest_swift.cc Jewel doesn't include boost/optional.hpp but has boost/utility/in_place_factory.hpp. The conflict has been resolved to pull in both headers.
rzarzynski
force-pushed
the
wip-16393-jewel
branch
from
August 16, 2016 13:08
c884a5c
to
dbf8cf0
Compare
@dachary: updated. |
ghost
pushed a commit
that referenced
this pull request
Aug 16, 2016
…ject versioning. Reviewed-by: Loic Dachary <ldachary@redhat.com>
ghost
pushed a commit
that referenced
this pull request
Aug 17, 2016
…ject versioning. Reviewed-by: Loic Dachary <ldachary@redhat.com>
@oritwas is this run of rgw http://tracker.ceph.com/issues/16344#note-27 good enough to merge this pull request ? |
yes, the failures are not related |
ghost
pushed a commit
that referenced
this pull request
Aug 22, 2016
…ject versioning. Reviewed-by: Loic Dachary <ldachary@redhat.com>
This pull request was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
http://tracker.ceph.com/issues/16393
Original PR: #9188.
CC: @dachary, @yehudasa, @oritwas.