[HDDS-1382] Create customized CSI server for Ozone

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Labels: pull-request-available
• Target Version/s: 0.5.0
• Assignee: Marton Elek
• Reporter: Marton Elek
• Created: 04/Apr/19 12:39
• Updated: 10/Apr/20 18:56
• Resolved: 31/May/19 12:16

Description

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.

Issue Links

• is related to: HDDS-3377 Remove guava 26.0-android jar
• links to: GitHub Pull Request #693