[
https://issues.apache.org/jira/browse/HDDS-1382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elek, Marton updated HDDS-1382:
-------------------------------
Status: Patch Available (was: Open)
> Create customized CSI server for Ozone
> --------------------------------------
>
> Key: HDDS-1382
> URL: https://issues.apache.org/jira/browse/HDDS-1382
> Project: Hadoop Distributed Data Store
> Issue Type: Sub-task
> Reporter: Elek, Marton
> Assignee: Elek, Marton
> Priority: Major
> Labels: pull-request-available
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> CSI (Container Storage Interface) is a vendor neutral storage interface
> specification for container orchestrators. CSI support is implemented in
> YARN, Kubernetes and Mesos. Implementing a CSI server makes it easy to mount
> disk volumes for containers.
> See https://github.com/container-storage-interface/spec for more details
> about the spec.
> Until now we used https://github.com/CTrox/csi-s3 server to support CSI
> specification. Using an ozone specific CSI server would have the following
> advantages:
> * We can provide additional functionalities (as we have access to the
> internal Ozone API not just the very generic s3 api).
> * Security setup can be synchronized.
> * Increased stability
> * Simplified deployment (only the minimal set of the components are required
> to be installed)
> The CSI specification itself is very simple
> (https://github.com/container-storage-interface/spec/blob/master/csi.proto)
> at least the part which is required for Ozone.
> We can use various fuse s3 driver to mount the ozone buckets via s3.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
