[
https://issues.apache.org/jira/browse/HDDS-4904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17299403#comment-17299403
]
Marton Elek edited comment on HDDS-4904 at 3/11/21, 8:33 AM:
-------------------------------------------------------------
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 (together with improved documentation) , and after
this patch we won't have any goofys in CSI any more.
bq. Is there a better and more functional option than goofys today?
Yes, certainly. There are many options. That's the point. Users may already
have s3 fuse driver which are already used by production. We should help the
integration and clarify where Ozone responsibilities ends.
bq. This is about facts, not opinions. It is about correctness and there is no
gray area. I am really disappointed at this argument. Let's do the right thing
instead of claiming CSI support to tick some checkmark.
It turns out that we have a different view about what is "the right thing". But
I totally agree to discuss technical terms and facts.
As I wrote earlier I think the production readiness of goofys and production
readiness of Ozone CSI driver are separated questions (see the linked commit)
was (Author: elek):
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]
