[
https://issues.apache.org/jira/browse/HDDS-4904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17298117#comment-17298117
]
Arpit Agarwal commented on HDDS-4904:
-------------------------------------
{quote}Because a lightweight CSI driver can do it automatically on-demand,
using a well-defined interface understood by container orchestrators
{quote}
Yes I understand the benefits of a proper CSI driver. The one we have currently
doesn't meet the bar.
{quote}The Ozone CSI daemon itself (which is responsible for creating the
bucket and executing the mount/umount operations) can be production ready. BUT
the mount command which is used by CSI can be or not be production ready,
depends on the choice of the options (goofys, s3fs-fuse, s3fuse or s3backer)
and the requirement (is POSIX security required? is caching required? read or
read only mounts are required?).
{quote}
This is not correct. We are advertising a solution based on s3 fuse but
essentially saying the limitations are not our problem, they are limitations in
the third party component.
{quote}But saying so that CSI driver is not production ready, BECAUSE goofys is
not production ready is confusing and can be mis-leading.
It's important to explain that the whole production-readiness depends on 3rd
party fuse drivers
{quote}
These technicalities don't matter to our users. If the end-end solution we are
providing to a user is not acceptable then we should not pass the buck and say
that the problem is with an external component and not ours.
The more I think I about it, the more I am inclined to completely remove CSI
support from the docs because even calling it a prototype suggests we are going
to make it better however this fuse based CSI driver is a dead end. We can
leave the driver in the build for now.
> Remove mention of CSI support
> -----------------------------
>
> Key: HDDS-4904
> URL: https://issues.apache.org/jira/browse/HDDS-4904
> Project: Apache Ozone
> Issue Type: Improvement
> Reporter: Arpit Agarwal
> Assignee: Dinesh Chitlangia
> Priority: Critical
>
> The Ozone website prominently mentions CSI support:
> [https://ozone.apache.org/docs/1.0.0/]
> [https://ozone.apache.org/docs/1.0.0/interface/csi.html]
> Our docs give a false impression to users that CSI is fully functional and
> supported for persistent storage inside containers.
> This support uses goofys+S3 gateway, so it is not appropriate for any serious
> usage. A real CSI solution should use an approach like the cBlocks prototype
> by building directly on top of HDDS containers with a real device driver.
> Until that time we should not claim CSI support. Alternatively we should be
> honest with our users that it is a prototype and not suitable for serious
> usage.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
