Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 20140200CD7 for ; Tue, 1 Aug 2017 19:17:08 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 1EA63163624; Tue, 1 Aug 2017 17:17:08 +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 642D71635A3 for ; Tue, 1 Aug 2017 19:17:07 +0200 (CEST) Received: (qmail 43125 invoked by uid 500); 1 Aug 2017 17:17:06 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 43114 invoked by uid 99); 1 Aug 2017 17:17:06 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Aug 2017 17:17:06 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id F39F0C0AFF for ; Tue, 1 Aug 2017 17:17:05 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id fVSE4ACP0P8x for ; Tue, 1 Aug 2017 17:17:05 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 79A235FD58 for ; Tue, 1 Aug 2017 17:17:04 +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 EB606E0E56 for ; Tue, 1 Aug 2017 17:17:03 +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 E284824DBF for ; Tue, 1 Aug 2017 17:17:02 +0000 (UTC) Date: Tue, 1 Aug 2017 17:17:02 +0000 (UTC) From: "Vrushali C (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-6820) Restrict read access to timelineservice v2 data MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 01 Aug 2017 17:17:08 -0000 [ https://issues.apache.org/jira/browse/YARN-6820?page=3Dcom.atlassian.= jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D16109= 343#comment-16109343 ]=20 Vrushali C commented on YARN-6820: ---------------------------------- Will add the license to the new unit test file I added in this patch. Also = will fix the checkstyle comments. The unit test failure is unrelated to the= patch and is being tracked in YARN-6874 > Restrict read access to timelineservice v2 data=20 > ------------------------------------------------ > > Key: YARN-6820 > URL: https://issues.apache.org/jira/browse/YARN-6820 > Project: Hadoop YARN > Issue Type: Sub-task > Components: timelineserver > Reporter: Vrushali C > Assignee: Vrushali C > Labels: yarn-5355-merge-blocker > Attachments: YARN-6820-YARN-5355.0001.patch > > > Need to provide a way to restrict read access in ATSv2. Not all users sho= uld be able to read all entities. On the flip side, some folks may not need= any read restrictions, so we need to provide a way to disable this access = restriction as well.=20 > Initially this access restriction could be done in a simple way via a whi= telist of users allowed to read data. That set of users can read all data, = no other user can read any data. Can be turned off for all users to read al= l data. > Could be stored in a "domain" table in hbase perhaps. Or a configuration = setting for the cluster. Or something else that's simple enough. ATSv1 has = a concept of domain for isolating users for reading. Would be good to keep = that in consideration.=20 > In ATSv1, domain offers a namespace for Timeline server allowing users to= host multiple entities, isolating them from other users and applications. = A =E2=80=9CDomain=E2=80=9D in ATSV1 primarily stores owner info, read and& = write ACL information, created and modified time stamp information. Each Do= main is identified by an ID which must be unique across all users in the YA= RN cluster. -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: yarn-issues-help@hadoop.apache.org