[
https://issues.apache.org/jira/browse/HDDS-4904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17299403#comment-17299403
]
Marton Elek commented on HDDS-4904:
-----------------------------------
bq. Then let's not document the goofys based solution in official docs. We can
put it in the cwiki as a prototype option
I think cwiki is for developer documentation, not for documenting implemented
features. For example because docs are included in all the daemons and
available runtime AND they are versioned together with the code.
As I wrote earlier the CSI driver (!!) is not "based" on goofys, goofys is just
one optional component. To make it more clear please check the following patch:
https://github.com/elek/ozone/commit/926b5bfe6bf9ef9309d9739953334ac0676d06ce
I am fine with committing it, and after this patch we won't have any goofys in
CSI any more.
> 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]
