I recently check the repo and the new version of s3cmd was released 3 days ago, including lifecycle commands:
2017-06-29 17:51 GMT+02:00 Daniel Gryniewicz <dang@xxxxxxxxxx>:
On 06/28/2017 02:30 PM, Graham Allan wrote:
That seems to be it! I couldn't see a way to specify the auth version
with aws cli (is there a way?). However it did work with s3cmd and v2 auth:
% s3cmd --signature-v2 setlifecycle lifecycle.xml s3://testgta
s3://testgta/: Lifecycle Policy updated
Good stuff.
(I believe that with Kraken, this threw an error and failed to set the
policy, but I'm not certain at this point... besides which radosgw
didn't then have access to the default.rgw.lc pool, which may have
caused further issues)
No way to read the lifecycle policy back with s3cmd, so:
I submitted a patch a while ago to add getlifecycle to s3cmd, and it was accepted, but I don't know about releases or distro packaging. It will be there eventually.
% aws --endpoint-url https://xxx.xxx.xxx.xxx s3api \
get-bucket-lifecycle-configuration --bucket=testgta
{
"Rules": [
{
"Status": "Enabled",
"Prefix": "",
"Expiration": {
"Days": 1
},
"ID": "test"
}
]
}
and looks encouraging at the server side:
# radosgw-admin lc list
[
{
"bucket": ":gta:default.6985397.1",
"status": "UNINITIAL"
},
{
"bucket": ":testgta:default.6790451.1",
"status": "UNINITIAL"
}
]
then:
# radosgw-admin lc process
and all the (very old) objects disappeared from the test bucket.
Good to know.
Daniel
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
Félix Barbeira.
_______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
