From hdfs-issues-return-207638-archive-asf-public=cust-asf.ponee.io@hadoop.apache.org Fri Jan 12 16:44:05 2018 Return-Path: X-Original-To: archive-asf-public@eu.ponee.io Delivered-To: archive-asf-public@eu.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by mx-eu-01.ponee.io (Postfix) with ESMTP id 03BCF180621 for ; Fri, 12 Jan 2018 16:44:05 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id E76DA160C42; Fri, 12 Jan 2018 15:44:04 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 387F0160C30 for ; Fri, 12 Jan 2018 16:44:04 +0100 (CET) Received: (qmail 59790 invoked by uid 500); 12 Jan 2018 15:44:03 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 59779 invoked by uid 99); 12 Jan 2018 15:44:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 12 Jan 2018 15:44:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id CB9D21A076C for ; Fri, 12 Jan 2018 15:44:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.911 X-Spam-Level: X-Spam-Status: No, score=-99.911 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id fiSXaVAxNCyF for ; Fri, 12 Jan 2018 15:44:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 5AFBC5F36A for ; Fri, 12 Jan 2018 15:44:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 99E24E0C18 for ; Fri, 12 Jan 2018 15:44:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 55EFD25BD0 for ; Fri, 12 Jan 2018 15:44:00 +0000 (UTC) Date: Fri, 12 Jan 2018 15:44:00 +0000 (UTC) From: "Elek, Marton (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HDFS-13017) Block Storage: implement simple iscsi discovery in jscsi server MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HDFS-13017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16324141#comment-16324141 ] Elek, Marton commented on HDFS-13017: ------------------------------------- The first version is uploaded. It just extends the existing protocolt to get the list of the available jscsi services. The easiest way to test is using docker-compose file from HDFS-12983, but you can also startup a new cblock server. After the creation of a cblock, you can test the discovery: ``` sudo iscsiadm -m discovery -t st -p 127.0.0.1:3260 ``` iscsi volumes should be detected and visible under the next call: ``` sudo iscsiadm -m node ``` > Block Storage: implement simple iscsi discovery in jscsi server > --------------------------------------------------------------- > > Key: HDFS-13017 > URL: https://issues.apache.org/jira/browse/HDFS-13017 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: ozone > Affects Versions: HDFS-7240 > Reporter: Elek, Marton > Assignee: Elek, Marton > Attachments: HDFS-13017-HDFS-7240.001.patch > > > The current jscsi server doesn't support iscsi discovery. > To use jscsi server as a kubernetes storage backend we need the discovery. jScsi supports it we need just override a method and add an additional call to the server protocl to get the list of the available cblocks. -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org