(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://github.com/ceph/ceph-csi >> https://github.com/ceph/ceph-csi/pulls >> >> CSI is a generic provisioning (and attachment) interface for container >> orchestration platforms, including Kubernetes and Mesos. >> >> https://github.com/container-storage-interface/spec >> >> 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 http://vger.kernel.org/majordomo-info.html > > -- > 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 -- 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
