[
https://issues.apache.org/jira/browse/HDDS-4904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17297559#comment-17297559
]
Dinesh Chitlangia commented on HDDS-4904:
-----------------------------------------
[~elek], [~arp] I would rather specify "not production ready" vs "alpha" just
to eliminate any misinterpretation.
What do you think of this?
{quote}
Ozone CSI support is not production ready and buckets can be mounted
only via 3rd party S3 compatible Fuse implementation (like Goofys). Fuse
over S3 can provide only limited performance compared to a native fuse file
systems. In the future, Ozone may support a custom solution to mount buckets
which provides better user experience (with fuse or NFS or any other
solution). Until then, CSI is recommended to use only if you can live with the
limitation, and your use case is tested carefully.
{quote}
> 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]
