Re: Fwd: S3 API Compatibility support

[M Ranga Swami Reddy <swamireddy@gmail.com>]

Hi ,

Could you please check and clarify the below question on object
lifecycle and notification S3 APIs support:

1. To support the bucket lifecycle - we need to support the
moving/deleting the objects/buckets based lifecycle settings.
For ex: If an object lifecyle set as below:
          1. Archive it after 10 days - means move this object to low
cost object storage after 10 days of the creation date.
           2. Remove this object after 90days - mean remove this
object from the low cost object after 90days of creation date.

Q1- Does the ceph support the above concept like moving to low cost
storage and delete from that storage?

2. To support the object notifications:
      - First there should be low cost and high availability storage
with single replica only. If an object created with this type of
object storage,
        There could be chances that object could lose, so if an object
of this type of storage lost, set the notifications.

Q2- Does Ceph support low cost and high availability storage type?

Thanks

On Fri, Sep 12, 2014 at 8:00 PM, M Ranga Swami Reddy
<swamireddy@gmail.com> wrote:
> Hi Yehuda,
>
> Could you please check and clarify the below question on object
> lifecycle and notification S3 APIs support:
>
> 1. To support the bucket lifecycle - we need to support the
> moving/deleting the objects/buckets based lifecycle settings.
> For ex: If an object lifecyle set as below:
>           1. Archive it after 10 days - means move this object to low
> cost object storage after 10 days of the creation date.
>            2. Remove this object after 90days - mean remove this
> object from the low cost object after 90days of creation date.
>
> Q1- Does the ceph support the above concept like moving to low cost
> storage and delete from that storage?
>
> 2. To support the object notifications:
>       - First there should be low cost and high availability storage
> with single replica only. If an object created with this type of
> object storage,
>         There could be chances that object could lose, so if an object
> of this type of storage lost, set the notifications.
>
> Q2- Does Ceph support low cost and high availability storage type?
>
> Thanks
> Swami
>
>
>
>
>
>
>
> On Tue, Jul 29, 2014 at 1:35 AM, Yehuda Sadeh <yehuda@redhat.com> wrote:
>> Bucket lifecycle:
>> http://tracker.ceph.com/issues/8929
>>
>> Bucket notification:
>> http://tracker.ceph.com/issues/8956
>>
>> On Sun, Jul 27, 2014 at 12:54 AM, M Ranga Swami Reddy
>> <swamireddy@gmail.com> wrote:
>>> Good no know the details. Can you please share the issue ID for bucket
>>> lifecycle? My team also could start help here.
>>> Regarding the notification - Do we have the issue ID?
>>> Yes, the object versioning will be backlog one - I strongly feel we
>>> start working on this asap.
>>>
>>> Thanks
>>> Swami
>>>
>>> On Fri, Jul 25, 2014 at 11:31 PM, Yehuda Sadeh <yehuda@redhat.com> wrote:
>>>> On Fri, Jul 25, 2014 at 10:14 AM, M Ranga Swami Reddy
>>>> <swamireddy@gmail.com> wrote:
>>>>> Thanks for quick reply.
>>>>> Yes,  versioned object - missing in ceph ATM
>>>>> Iam looking for: bucket lifecylce (get/put/delete), bucket location,
>>>>> put object notification and object restore (ie versioned object) S3
>>>>> API support.
>>>>> Please let me now any of the above work is in progress or some one
>>>>> planned to work on.
>>>>
>>>>
>>>> I opened an issue for bucket lifecycle (we already had an issue open
>>>> for object expiration though). We do have bucket location already
>>>> (part of the multi-region feature). Object versioning is definitely on
>>>> our backlog and one that we'll hopefully implement sooner rather
>>>> later.
>>>> With regard to object notification, it'll require having a
>>>> notification service which is a bit out of the scope. Integrating the
>>>> gateway with such a service whouldn't be hard, but we'll need to have
>>>> that first.
>>>>
>>>> Yehuda
>>>>
>>>>>
>>>>> Thanks
>>>>> Swami
>>>>>
>>>>>
>>>>> On Fri, Jul 25, 2014 at 9:19 PM, Sage Weil <sweil@redhat.com> wrote:
>>>>>> On Fri, 25 Jul 2014, M Ranga Swami Reddy wrote:
>>>>>>> Hi Team: As per the ceph document a few S3 APIs compatibility not supported.
>>>>>>>
>>>>>>> Link: http://ceph.com/docs/master/radosgw/s3/
>>>>>>>
>>>>>>> Is there plan to support the ?n supported item in the above table?
>>>>>>> or
>>>>>>> Any working on this?
>>>>>>
>>>>>> Yes.  Unfortunately this table isn't particularly detailed or accurate or
>>>>>> up to date.   The main gap, I think, is versioned objects.
>>>>>>
>>>>>> Are there specfiic parts of the S3 API that are missing that you need?
>>>>>> That sort of info is very helpful for prioritizing effort...
>>>>>>
>>>>>> sage
>>>>> --
>>>>> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
>>>>> the body of a message to majordomo@vger.kernel.org
>>>>> More majordomo info at  http://vger.kernel.org/majordomo-info.html