Bug 1314580
| Summary: | [RFE] RGW: support swift bulk delete | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Yehuda Sadeh <yehuda> |
| Component: | RGW | Assignee: | Yehuda Sadeh <yehuda> |
| Status: | CLOSED ERRATA | QA Contact: | shilpa <smanjara> |
| Severity: | medium | Docs Contact: | Bara Ancincova <bancinco> |
| Priority: | unspecified | ||
| Version: | 2.0 | CC: | asriram, bancinco, cbodley, ceph-eng-bugs, gmeno, hnallurv, kbader, kdreyer, mbenjamin, nlevine, owasserm, sweil, yehuda |
| Target Milestone: | rc | Keywords: | FutureFeature |
| Target Release: | 2.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: |
.Support for Swift `bulk-delete` has been added
Red Hat Ceph Storage now supports the Swift `bulk-delete` feature. With this new feature, users can delete multiple objects from an account with a single request.
For details see the https://access.redhat.com/documentation/en/red-hat-openstack-platform/8/single/configuration-reference/#object-storage-bulk-delete[Bulk delete] section in the https://access.redhat.com/documentation/en/red-hat-openstack-platform/8/single/configuration-reference[Configuration Reference] guide for Red Hat OpenStack Platform 8.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-08-23 19:33:12 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1322504 | ||
|
Description
Yehuda Sadeh
2016-03-04 00:32:50 UTC
I take Yehuda's comment above to mean that this bug relates to the Swift SLO RFE in bug 1283407 Hi Bara, Please add a link to openstack doc that explains how to perform a bulk delete. Thanks Bara. Moving to verified. 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-2016:1755 |