Hi Huamin,
Serguei mention that the current effort is to get ceph-csi driver to be feature compatible with the in-tree RBD plugin in K8s. However, doing this will not benefit Rook. There are lots of gaps in the current RBD implementation such as user/secret management, update of monitoring endpoints and ROX support to name a few. Which is the reason Rook explored to using a Flexvolume.
What is the strategy of ceph-csi around also supporting Rook’s needs?
On 1/11/18, 10:42 AM, "Huamin Chen" <hchen@xxxxxxxxxx> wrote:
(resending, previous reply bounced back)
Hi Bassam,
Thanks for the suggestions.
Having a CSI repo is a great first step. Now Serguei is putting up a
prototype as PR #1. It mirrors the current k8s in tree rbd volume
plugin.
Since the project just starts, there is no formal meetings and process
management. Since not every contributor here use Ceph tracker, I
propose to use github issues for issue and bug tracking, feature
request, and assignment so we can track topics like krbd/nbd, cephfs
and fuse.
On Wed, Jan 10, 2018 at 5:29 PM, Bassam Tabbara <bassam@xxxxxxxxxxx> wrote:
> Excellent! Excited to see this work starting.
>
> Could we please get a blueprint/design on ceph-csi written down and reviewed?
>
> There are a lot of different topics to consider here around secret management, user-mode vs. kernel, etc. that might be better sorted in a design doc vs. in PR reviews.
>
> (cc’ing steve that offered to help)
>
>> On Jan 10, 2018, at 10:45 AM, Sage Weil <sweil@xxxxxxxxxx> wrote:
>>
>> Development has kicked off on a CSI driver for Ceph (RBD initially; CephFS
>> will follow). See
>>
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fceph%2Fceph-csi&data=02%7C01%7CSteve.LeonTang%40quantum.com%7C304b1dcf913842527a4208d559230624%7C322a135f14fb4d72aede122272134ae0%7C1%7C0%7C636512929325908407&sdata=%2BbN2phVfQ5%2BQJCwGypH%2BNo4JKuH1xmbiLl99km8aYbo%3D&reserved=0
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fceph%2Fceph-csi%2Fpulls&data=02%7C01%7CSteve.LeonTang%40quantum.com%7C304b1dcf913842527a4208d559230624%7C322a135f14fb4d72aede122272134ae0%7C1%7C0%7C636512929325908407&sdata=Xr9VWhIi%2FlN%2FwDAzxOZU1lj2rU%2FywD5U9dD0lHuvImg%3D&reserved=0
>>
>> CSI is a generic provisioning (and attachment) interface for container
>> orchestration platforms, including Kubernetes and Mesos.
>>
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fcontainer-storage-interface%2Fspec&data=02%7C01%7CSteve.LeonTang%40quantum.com%7C304b1dcf913842527a4208d559230624%7C322a135f14fb4d72aede122272134ae0%7C1%7C0%7C636512929325908407&sdata=8KgV3ZuUX7%2BdXxJpoe2sz1INodEoNzEFVoxA7PefXeQ%3D&reserved=0
>>
>> In the kubernetes context, this will /eventually/ replace the in-tree RBD
>> and CephFS volume drivers, as well as Rook's flex volume plugin.
>>
>> sage
>> --
>> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
>> the body of a message to majordomo@xxxxxxxxxxxxxxx
>> More majordomo info at https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fvger.kernel.org%2Fmajordomo-info.html&data=02%7C01%7CSteve.LeonTang%40quantum.com%7C304b1dcf913842527a4208d559230624%7C322a135f14fb4d72aede122272134ae0%7C1%7C0%7C636512929325908407&sdata=C7mInLBxcIFneCsNgIwp9K66BoV238y8BPc9m3p4d3U%3D&reserved=0
>
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fvger.kernel.org%2Fmajordomo-info.html&data=02%7C01%7CSteve.LeonTang%40quantum.com%7C304b1dcf913842527a4208d559230624%7C322a135f14fb4d72aede122272134ae0%7C1%7C0%7C636512929325908407&sdata=C7mInLBxcIFneCsNgIwp9K66BoV238y8BPc9m3p4d3U%3D&reserved=0
The information contained in this transmission may be confidential. Any disclosure, copying, or further distribution of confidential information is not permitted unless such privilege is explicitly granted in writing by Quantum. Quantum reserves the right to have electronic communications, including email and attachments, sent across its networks filtered through security software programs and retain such messages in order to comply with applicable data security and retention requirements. Quantum is not responsible for the proper and complete transmission of the substance of this communication or for any delay in its receipt.
��.n��������+%������w��{.n����z��u���ܨ}���Ơz�j:+v�����w����ޙ��&�)ߡ�a����z�ޗ���ݢj��w�f
