Conversation
595c080 to
8469c77
Compare
|
cc @yehudasa |
|
some radosgw-admin failures, and lots of valgrind issues to go through: http://pulpito.ceph.com/cbodley-2019-07-26_18:05:13-rgw-wip-cbodley-testing-distro-basic-smithi/ |
|
from qa/tasks/radosgw_admin.py, the creation of user2=fud fails during |
Signed-off-by: Yehuda Sadeh <yehuda@redhat.com>
Signed-off-by: Yehuda Sadeh <yehuda@redhat.com>
move code out of RGWRados, refactor a bit to use rados svc. Signed-off-by: Yehuda Sadeh <yehuda@redhat.com>
Dependency reduction Signed-off-by: Yehuda Sadeh <yehuda@redhat.com>
cascading changes, and minor improvements. Signed-off-by: Yehuda Sadeh <yehuda@redhat.com>
Signed-off-by: Yehuda Sadeh <yehuda@redhat.com>
Signed-off-by: Yehuda Sadeh <yehuda@redhat.com>
Consolidate objclass util services. Signed-off-by: Yehuda Sadeh <yehuda@redhat.com>
Signed-off-by: Yehuda Sadeh <yehuda@redhat.com>
Signed-off-by: Yehuda Sadeh <yehuda@redhat.com>
Signed-off-by: Yehuda Sadeh <yehuda@redhat.com>
Signed-off-by: Yehuda Sadeh <yehuda@redhat.com>
Signed-off-by: Yehuda Sadeh <yehuda@redhat.com>
move implementation out of header. Signed-off-by: Yehuda Sadeh <yehuda@redhat.com>
Signed-off-by: Yehuda Sadeh <yehuda@redhat.com>
Signed-off-by: Yehuda Sadeh <yehuda@redhat.com>
I didn't intend for it to be such a big commit, and it's not even compiling yet. This changes the structure of how the metadata manager and handlers work. The idea is to be able to relatively easily hook in different meta backends (or same backends with different handling -- such as the otp). Added new services for meta, meta backend, and meta backend sysobj implementation. The meta backend service is responsible for the final data storage, and updating the meta log (log might be split later on, but at the moment it keeping it together for simplicity). The handlers themselves are the ones responsible for reading or modifying the metadata. This means that they need to call the meta backend service instead of calling the utility functions. The utility functions need to call the handlers, and not the other way around. Handlers can have utility methods to assist. Left to do: get everything actually compiling and implemented. The structure is there, now need to fill in the gaps. Signed-off-by: Yehuda Sadeh <yehuda@redhat.com>
|
the valgrind leak was because RGWSI_MetaBackend_Handler::Op doesn't have a virtual destructor, so the derived Op_ManagedCtx destructor isn't called to delete the allocated Context. since Op doesn't have any other virtual methods, i decided against making its destructor virtual. instead, i pushed a commit that uses the public Op_ManagedCtx directly |
|
next failure is in radosgw_admin_rest on test case |
Signed-off-by: Casey Bodley <cbodley@redhat.com>
src/rgw/rgw_bucket.cc
Outdated
|
|
||
| // ...and encode the acl | ||
| attrs[RGW_ATTR_ACL].clear(); | ||
| policy.encode(attrs[RGW_ATTR_ACL]); |
There was a problem hiding this comment.
this was missing the call to clear(), so re-encoding the policy was appending to the old one and not taking effect
There was a problem hiding this comment.
@cbodley looks good, but maybe can do it like this:
auto& attr = atts[RGW_ATTR_ACL]; attr.clear(); policy.encode(attr);
to avoid a double lookup?
|
http://pulpito.ceph.com/cbodley-2019-08-01_13:07:49-rgw-wip-cbodley-testing-distro-basic-smithi/ looks like a pass. i'll start rebasing this on top of #28813 so we can merge both |
dd0e60d to
8f912a6
Compare
|
i squashed everything into a single commit (because individual commits did not compile on their own), and rebased on top of #29540 |
|
@yehudasa how much of the history is history just of the evolution of metadata refactor in your checkout? |
|
@mattbenjamin I can't really say. History can have value, even if not immediately clear. Squashing everything and applying a single commit is technically the same as running git merge. Is there a reason to lose all the history? |
8f912a6 to
3e7dc95
Compare
Signed-off-by: Casey Bodley <cbodley@redhat.com>
f5d6064 to
96cbc98
Compare
Conflicts: src/rgw/rgw_auth.cc src/rgw/rgw_auth_registry.h src/rgw/rgw_auth_s3.h src/rgw/rgw_bucket.cc src/rgw/rgw_bucket.h src/rgw/rgw_data_sync.h src/rgw/rgw_frontend.h src/rgw/rgw_log.h src/rgw/rgw_main.cc src/rgw/rgw_rados.cc src/rgw/rgw_rados.h src/rgw/rgw_rest_s3.h src/rgw/rgw_rest_sts.h src/rgw/rgw_swift_auth.h src/rgw/rgw_user.cc src/rgw/rgw_user.h src/rgw/services/svc_sys_obj_core.h
96cbc98 to
75e1ec8
Compare
|
mostly passed in http://pulpito.ceph.com/cbodley-2019-08-13_12:16:43-rgw-wip-cbodley-testing-distro-basic-smithi/ some |
|
@cbodley no objections |
|
Please run the Dashboard QA test suites before next time to ensure RGW changes do not break the Dashboard or inform the Dashboard team and open a tracker issue with the changes that needs to be adapted in the Dashboard. |
|
@votdev i don't think it's reasonable to run every rgw pr through an extra teuthology suite. i'd prefer to move the dashboard's functional test coverage of rgw admin apis into qa/tasks/radosgw_admin_rest.py which runs as part of the rgw suite |
| return -EINVAL; | ||
| } | ||
| rgw_bucket old_bucket = bucket; | ||
| bucket.tenant = tenant; |
There was a problem hiding this comment.
oops, somehow this change snuck into the rebase
rebase of #28679 with some additional cleanup