Bug 1445891
| Summary: | [RFE] Add custom user data support in bucket index | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Benjamin Schmaus <bschmaus> |
| Component: | RGW | Assignee: | Matt Benjamin (redhat) <mbenjamin> |
| Status: | CLOSED ERRATA | QA Contact: | Vasishta <vashastr> |
| Severity: | high | Docs Contact: | Bara Ancincova <bancinco> |
| Priority: | unspecified | ||
| Version: | 2.2 | CC: | cbodley, ceph-eng-bugs, kbader, kdreyer, mbenjamin, mhackett, owasserm, sweil, tserlin, uboppana, vakulkar, vashastr, vumrao |
| Target Milestone: | rc | Keywords: | FutureFeature |
| Target Release: | 2.3 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | RHEL: ceph-10.2.7-28.el7cp Ubuntu: ceph_10.2.7-30redhat1 | Doc Type: | Bug Fix |
| Doc Text: |
The Ceph Object Gateway now supports a mechanism to associate opaque data to the object entries in internal bucket index metadata, and to recover this uninterpreted data in a custom HTTP header in bucket listing operations. This new feature enables users to store any user-defined data in the bucket index. Currently, interfaces to set and return user data are only available using the Swift access protocol.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-07-17 17:06:06 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Benjamin Schmaus
2017-04-26 17:38:31 UTC
looks great, thanks Bara Hi all,
Working fine for me, moving to VERIFIED state.
$ sudo radosgw-admin bucket list --bucket test_z --cluster 1 |grep user_data
"user_data": "ABCD_MNOP"
"user_data": "ABCD_1234"
"user_data": "1234_5678"
Regards,
Vasishta
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:1755 |