hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Work logged] (HDDS-1382) Create customized CSI server for Ozone
Date Thu, 30 May 2019 15:51:00 GMT

     [ https://issues.apache.org/jira/browse/HDDS-1382?focusedWorklogId=251045&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-251045

ASF GitHub Bot logged work on HDDS-1382:

                Author: ASF GitHub Bot
            Created on: 30/May/19 15:50
            Start Date: 30/May/19 15:50
    Worklog Time Spent: 10m 
      Work Description: anuengineer commented on issue #693: HDDS-1382. Create customized
CSI server for Ozone.
URL: https://github.com/apache/hadoop/pull/693#issuecomment-497379555
   +1, @elek  Can you please fix the checkstyle issues while committing ? Thanks
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

Issue Time Tracking

    Worklog Id:     (was: 251045)
    Time Spent: 3h  (was: 2h 50m)

> 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: 3h
>  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

To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org

View raw message