[
https://issues.apache.org/jira/browse/HDDS-4904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17299043#comment-17299043
]
Arpit Agarwal edited comment on HDDS-4904 at 3/10/21, 6:21 PM:
---------------------------------------------------------------
{quote}Are you talking about the limitations of goofys? What I try to explain
is that goofys is just one, optional element of the picture as any other fuse
file systems can be used.
{quote}
Is there a better and more functional option than goofys today?
{quote}What I am saying is that the vendor distributions are better place for
opinionated decisions. While a vendor has the responsibility to define what is
production ready, an Apache project may be more inclusive as the final decision
should be the responsibility of the end-user. I think, the responsibility of us
(developers of open source Apache Ozone) is clearly communicate the risks.
Obviously there are problems which should be avoided everywhere (like security
holes), but this decision (is there any production ready s3 fuse file system?)
is not black and white for me.
{quote}
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.
was (Author: arpitagarwal):
{quote}Are you talking about the limitations of goofys? What I try to explain
is that goofys is just one, optional element of the picture as any other fuse
file systems can be used.
{quote}
Is there a better and more functional option than goofys today?
{quote}What I am saying is that the vendor distributions are better place for
opinionated decisions. While a vendor has the responsibility to define what is
production ready, an Apache project may be more inclusive as the final decision
should be the responsibility of the end-user. I think, the responsibility of us
(developers of open source Apache Ozone) is clearly communicate the risks.
Obviously there are problems which should be avoided everywhere (like security
holes), but this decision (is there any production ready s3 fuse file system?)
is not black and white for me.
{quote}
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 off some checkmark.
> 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]
