--
You received this message because you are subscribed to the Google Groups "container-storage-interface-community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to container-storage-interf...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/container-storage-interface-community/9770c558-82c7-47a9-b930-9a4d9ed810c6%40googlegroups.com.
AFAIK, you are correct in that the CSI Spec does not prevent it. Also, our driver (Portworx) supports RWO and RWX on the same driver. That is all up to the storage system and is driver specific. I think GlusterFS also supports RWO and RWX, and maybe Ceph?
- Luis--On Wed, Aug 7, 2019 at 9:34 PM Sandeep P S <sandee...@gmail.com> wrote:Hi,--I have been rereading the CSI API spec and Kubernetes CSI design spec to see if the CSI spec has made any explicit assumption that a single CSI driver cannot support read write once(RWO), read only many(ROX) and read write many(RWX) volumes in a single driver. So, far, I have not come across anything that prevents a CSI driver to support all volume types. Can someone in this group confirm/deny this?I also see that many cloud vendors have separate CSI drivers for RWO(block/disk volumes) and RWX (file shares). I'm wondering why they built it as separate drivers and not combine them into a single driver. Any clues? And I'm also wondering if this is somehow connected to CSI spec not supporting it. Any details on this is appreciated.Thanks,Sandeep
You received this message because you are subscribed to the Google Groups "container-storage-interface-community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to container-storage-interf...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/container-storage-interface-community/9770c558-82c7-47a9-b930-9a4d9ed810c6%40googlegroups.com.
You received this message because you are subscribed to the Google Groups "container-storage-interface-community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to container-storage-interf...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/container-storage-interface-community/CAEvoFsEEkZCLhCWQANXmvZ-PFHV5k7g8Dnu3%2BGCujHM9RKRo4g%40mail.gmail.com.
On Wed, Aug 7, 2019 at 7:42 PM Luis Pabon <lu...@portworx.com> wrote:AFAIK, you are correct in that the CSI Spec does not prevent it. Also, our driver (Portworx) supports RWO and RWX on the same driver. That is all up to the storage system and is driver specific. I think GlusterFS also supports RWO and RWX, and maybe Ceph?Agreed, and yes the Ceph plugin supports this as well, I believe there are others, or soon will be.
- Luis
On Wed, Aug 7, 2019 at 9:34 PM Sandeep P S <sande...@gmail.com> wrote:
Hi,--I have been rereading the CSI API spec and Kubernetes CSI design spec to see if the CSI spec has made any explicit assumption that a single CSI driver cannot support read write once(RWO), read only many(ROX) and read write many(RWX) volumes in a single driver. So, far, I have not come across anything that prevents a CSI driver to support all volume types. Can someone in this group confirm/deny this?I also see that many cloud vendors have separate CSI drivers for RWO(block/disk volumes) and RWX (file shares). I'm wondering why they built it as separate drivers and not combine them into a single driver. Any clues? And I'm also wondering if this is somehow connected to CSI spec not supporting it. Any details on this is appreciated.Thanks,Sandeep
You received this message because you are subscribed to the Google Groups "container-storage-interface-community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to container-storage-interface-community+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/container-storage-interface-community/9770c558-82c7-47a9-b930-9a4d9ed810c6%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "container-storage-interface-community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to container-storage-interface-community+unsubscribe@googlegroups.com.