Ceph » rgw

Does this work in openstack's swift? My understanding is that expiration and slo are both implemented as middleware, and I don't see any documentation about how they interact. Looking at the swift-object-expirer source at https://github.com/openstack/swift/blob/master/swift/obj/expirer.py#L481, it appears to be sending normal DELETE requests without the ?multipart-manifest=delete parameter that would also delete its segments.

Are you uploading with a swift client command similar to this?

swift upload container obj -S 4M -H "X-Delete-At:..." 

This command only adds the expiration header to the final request that writes the manifest, and not for any of the segment uploads. That's why radosgw's object expirer doesn't consider the segments for expiration.

And while the swift client generally uploads and deletes the segments transparently, the underlying SLO api is more flexible - for example, nothing prevents two different object manifests from referring to the same segment objects, or from referring to segments that were uploaded as normal swift objects. So if the X-Delete-At header on one of those manifests expired its segments by default, that would corrupt unrelated objects.

On the other hand, if an environment uses the swift client exclusively to manage these segments, it should be safe to provide them the option to expire them along with their manifest. Maybe a new header such as 'x-rgw-expire-segments' would be a reasonable way for clients to express this intent?

Changing this to a feature request, as our behavior appears to match openstack's.