[
https://issues.apache.org/jira/browse/HDDS-4904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17300073#comment-17300073
]
Marton Elek commented on HDDS-4904:
-----------------------------------
> Okay so there is no good solution
Well, with quick google I see a lot of promising solution which seems to be
mature. So there ARE multiple solutions which can be judged as good or not.
> I really suggest you go and look at some of the other open source CSI
> providers and the effort they put in before declaring CSI support.
You mean declaring CSI support as "production-ready", I guess. Anyway I would
be very happy to spend more time with testing and comparing the available
options and add them to the documentation.
(However, still I think it's the responsibility of the user of open source
Ozone or the responsibility of the vendor to judge which s3 fuse driver is
acceptable for a given use case/production environment. But it's a good idea to
help this decision with more documentation.)
> 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]
