You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2019/05/21 19:10:00 UTC
[jira] [Work logged] (HDDS-1382) Create customized CSI server for
Ozone
[ https://issues.apache.org/jira/browse/HDDS-1382?focusedWorklogId=246316&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-246316 ]
ASF GitHub Bot logged work on HDDS-1382:
----------------------------------------
Author: ASF GitHub Bot
Created on: 21/May/19 19:09
Start Date: 21/May/19 19:09
Worklog Time Spent: 10m
Work Description: ajayydv commented on pull request #693: HDDS-1382. Create customized CSI server for Ozone.
URL: https://github.com/apache/hadoop/pull/693#discussion_r286181017
##########
File path: hadoop-hdds/common/src/main/resources/ozone-default.xml
##########
@@ -2400,8 +2400,14 @@
<name>hdds.tracing.enabled</name>
<value>true</value>
<tag>OZONE, HDDS</tag>
+ <description>If enabled, tracing information is sent to tracing server.</description>
+ </property>
+ <property>
+ <name>ozone.s3g.address</name>
+ <value/>
+ <tag>OZONE, MANAGEMENT</tag>
<description>
- If enabled, tracing information is sent to tracing server.
+ The address of the Ozone S3G gateway.n.
Review comment:
typo in end?
----------------------------------------------------------------
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:
users@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 246316)
Time Spent: 1.5h (was: 1h 20m)
> 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: 1.5h
> 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: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org