Hi~ Yehuda and Ceph developers: We're trying to implement S3 feature bucket logging (http://docs.aws.amazon.com/AmazonS3/latest/dev/ServerLogs.html). Currently RGW didn't support bucket logging(http://tracker.ceph.com/issues/3225),but has similar functionality called opslog. RGW opslog has its own CLI API,opslog can be accessed only by radosgw-admin CLI API(radosgw-admin log list/show). In order to compatible with S3, we're trying to adapt current opslog to support S3 bucket logging HTTP API via RGW s3 endpoint. Does this make sense for RGW? Caz I've found we tried to impl ops log HTTP API via admin endpoint(https://github.com/ceph/ceph/pull/7859) If the answer is yes,we'd like to share our plan.The basic idea to impl bucket logging takes two steps: 1) Reuse current ops log (rgw_ops_log_rados)impl as a temp&durable storage(ops log be stored as a rados-object) 2) Add a new thread periodically upload opslog rados-object as rgw-object more detailed steps: 1) impl bucket logging HTTP config API + GET bucket logging + PUT bucket logging + store bucket logging config into bucket attribute + add new entry(<bucket_name,bucket_logging_status>) to a sharded <bucket_logging.X> rados-object's omap in <.rgw.bl> pool (<bucket_logging.X>'s omap head store a marker to track progress) + ACL support Log Delivery Group 2) impl ops log deliver logic + upload rados-object as rgw-object(or to avoid extra data transfer,can we map a rados-obj to a rgw-object by editing its manifiest?) + (optional) trim opslog 3) impl bucket logging CLI API + radosgw-admin bl list // list all bucket logging progress + radosgw-admin bl deliver // manually deliver ops log Any comments are appreciated.Thx. -- mikuley -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
