Hi!
I use the aws CLI tool, like this:
aws --endpoint-url=http://your-rgw:7480 s3api put-bucket-versioning
--bucket yourbucket --versioning-configuration Status=Enabled
I also set a lifecycle configuration to expire older versions, e.g.:
aws --endpoint-url=http://your-rgw:7480 s3api
put-bucket-lifecycle-configuration --bucket yourbucket
--lifecycle-configuration file:///path/to/your/lifecycle.json
Lifecycle configuration example:
{
"Rules": [{
"Status": "Enabled",
"Prefix": "",
"NoncurrentVersionExpiration": {
"NoncurrentDays": 60
},
"Expiration": {
"ExpiredObjectDeleteMarker": true
},
"ID": "expire-60days"
}]
}
But I am not sure how stable the versioning and lifecycle features in
Ceph are, I suspect that some of my issues with the rados gateway relate
to using versioning and lifecycle rules. Maybe someone can comment on that.
Regards,
Martin
Am 03.01.18 um 11:41 schrieb [email protected]:
hi
i'm using s3cmd ( version 1.6.1) to put object to ceph cluster
(jewel 10.2.10),
and when i put the file with the same name, the older one is overrided.
i know that rgw supports bucket object version. But how can i
enabled it when using s3cmd?
thanks
------------------------------------------------------------------------
[email protected]
_______________________________________________
ceph-users mailing list
[email protected]
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
_______________________________________________
ceph-users mailing list
[email protected]
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
