[
https://issues.apache.org/jira/browse/HDDS-4904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17298630#comment-17298630
]
Marton Elek commented on HDDS-4904:
-----------------------------------
bq. "Your understanding" is a very nebulous way to justify it. How it can be a
good solution with the security, performance and POSIX API limitations?
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.
bq. Are you saying the quality bar for Apache Ozone should be lower? I disagree.
No, I am not saying that. I agree that the quality bar should be the highest
everywhere.
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. Couldn't be decided without knowing the
production requirements.
For example without SCM-HA, Ozone has a SPOF. Instead of saying it's not
production ready we clearly communicate the risks and how we will solve this
long-term. Becuase there could be use cases where it's acceptable (for example
storing temporary, or shuffle data on Ozone?)
At least this is my personal view.
> 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]
