From yarn-issues-return-137038-archive-asf-public=cust-asf.ponee.io@hadoop.apache.org Fri Feb 2 05:03: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 7255F180652 for ; Fri, 2 Feb 2018 05:03:05 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 61FB2160C44; Fri, 2 Feb 2018 04:03:05 +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 82B1A160C56 for ; Fri, 2 Feb 2018 05:03:04 +0100 (CET) Received: (qmail 68461 invoked by uid 500); 2 Feb 2018 04:03:03 -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 68387 invoked by uid 99); 2 Feb 2018 04:03:03 -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; Fri, 02 Feb 2018 04:03:03 +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 1724CE84E7 for ; Fri, 2 Feb 2018 04:03:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.511 X-Spam-Level: X-Spam-Status: No, score=-109.511 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_SPF_WL=-7.5, 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 2FuGRD53Rcml for ; Fri, 2 Feb 2018 04:03:02 +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 D636E5F2A9 for ; Fri, 2 Feb 2018 04:03: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 297E5E02F7 for ; Fri, 2 Feb 2018 04:03:01 +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 4D54F21E89 for ; Fri, 2 Feb 2018 04:03:00 +0000 (UTC) Date: Fri, 2 Feb 2018 04:03:00 +0000 (UTC) From: "LiangYe (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (YARN-7854) Attach prefixes to different type of node attributes MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/YARN-7854?page=3Dcom.atlassian.= jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D16349= 752#comment-16349752 ]=20 LiangYe edited comment on YARN-7854 at 2/2/18 4:02 AM: ------------------------------------------------------- In k8s=EF=BC=8C=C2=A0[Namespace|https://github.com/kubernetes/community/blo= b/master/contributors/design-proposals/architecture/namespaces.md]=C2=A0=C2= =A0is a mechanism to partition resources created by users into logically na= med group. The=C2=A0=C2=A0[Namespace|https://kubernetes.io/docs/concepts/overview/work= ing-with-objects/namespaces/]=C2=A0provides a unique scope for: # named resources (pods, services, replication controllers, etc. to avoid = basic naming collisions, {color:#ff0000}*now not include nodes and persista= ntVolume*{color}) # delegated management authority to trusted users # ability to limit community resource consumption In k8s,=C2=A0_Labels_=C2=A0are key/value pairs that are attached to objects= , such as pods, nodes.=C2=A0=C2=A0Valid label keys have two segments: an op= tional prefix and name, separated by a slash ({{/}}).=C2=A0=C2=A0If the pre= fix is omitted, the label Key is presumed to be private to the user. Automa= ted system components (e.g.=C2=A0{{kube-scheduler}},=C2=A0{{kube-controller= -manager}},=C2=A0{{kube-apiserver}},=C2=A0{{kubectl}}, or other third-party= automation) which add labels to end-user objects must specify a prefix. Th= e=C2=A0{{kubernetes.io/}}=C2=A0prefix is reserved for Kubernetes core compo= nents. In k8s, according to different object's labels, there is different affinity= , e.g. [node labels=E2=80=94=E2=80=94node affinity|https://github.com/kuber= netes/community/blob/master/contributors/design-proposals/scheduling/nodeaf= finity.md], [pod labels=E2=80=94=E2=80=94pod affinity|https://github.com/ku= bernetes/community/blob/master/contributors/design-proposals/scheduling/pod= affinity.md].=C2=A0 Especially [node taints=E2=80=94=E2=80=94pod toleration= |https://github.com/kubernetes/community/blob/master/contributors/design-pr= oposals/scheduling/taint-toleration-dedicated.md]. In yarn, according to=C2=A0 YARN-3409=C2=A0=C2=A0 YARN-6592=C2=A0 [#YARN-78= 00]=C2=A0=C2=A0and so, node attribute is like k8s node labels,=C2=A0allocat= ion tags to container is like k8s pod labels but in k8s pod labels not deli= very to nodes for namespace isolation, node constraint is some kind of k8s = taints and tolerations. So to this Jira issue, to make up prefix for node attributes from different= =C2=A0 sources is a kind of namespace isolation.=C2=A0 For now,=C2=A0 # Centralized: attributes set by users (admin or normal users) can use a p= refix like {color:#ff0000}yarn_rm_admin/{color} # Distributed: attributes collected by a certain attribute provider on eac= h NM can use a prefix like {color:#ff0000}yarn_nm/{color} # System: some built-in attributes in yarn, set by yarn internal component= s, e.g scheduler like {color:#ff0000}yarn_system/{color} then, In RM merge from these sources, no need to handle the conflict cases. In placement constraints for node attributes should specify prefix to=C2=A0= indicate the sources/namespaces, or use yarn_nm/ prefix by default. [~cheersyang] [~leftnoteasy] [~Naganarasimha]=C2=A0 any comment?=C2=A0 Than= ks. was (Author: lambertye): In k8s=EF=BC=8C=C2=A0[Namespace|https://github.com/kubernetes/community/blo= b/master/contributors/design-proposals/architecture/namespaces.md]=C2=A0=C2= =A0is a mechanism to partition resources created by users into logically na= med group. =C2=A0 The=C2=A0=C2=A0[Namespace|https://kubernetes.io/docs/concepts/overview/work= ing-with-objects/namespaces/]=C2=A0provides a unique scope for: # named resources (pods, services, replication controllers, etc. to avoid = basic naming collisions, {color:#FF0000}*now not include nodes and persista= ntVolume*{color}) # delegated management authority to trusted users # ability to limit community resource consumption In k8s,=C2=A0_Labels_=C2=A0are key/value pairs that are attached to objects= , such as pods, nodes.=C2=A0=C2=A0Valid label keys have two segments: an op= tional prefix and name, separated by a slash ({{/}}).=C2=A0=C2=A0If the pre= fix is omitted, the label Key is presumed to be private to the user. Automa= ted system components (e.g.=C2=A0{{kube-scheduler}},=C2=A0{{kube-controller= -manager}},=C2=A0{{kube-apiserver}},=C2=A0{{kubectl}}, or other third-party= automation) which add labels to end-user objects must specify a prefix. Th= e=C2=A0{{kubernetes.io/}}=C2=A0prefix is reserved for Kubernetes core compo= nents. In k8s, according to different object's labels, there is different affinity= , e.g. [node labels=E2=80=94=E2=80=94node affinity|https://github.com/kuber= netes/community/blob/master/contributors/design-proposals/scheduling/nodeaf= finity.md], [pod labels=E2=80=94=E2=80=94pod affinity|https://github.com/ku= bernetes/community/blob/master/contributors/design-proposals/scheduling/pod= affinity.md].=C2=A0 Especially [node taints=E2=80=94=E2=80=94pod toleration= |https://github.com/kubernetes/community/blob/master/contributors/design-pr= oposals/scheduling/taint-toleration-dedicated.md]. In yarn, according to=C2=A0 YARN-3409=C2=A0=C2=A0 YARN-6592=C2=A0 [#YARN-78= 00]=C2=A0=C2=A0and so, node attribute is like k8s node labels,=C2=A0allocat= ion tags to container is like k8s pod labels but in k8s pod labels not deli= very to nodes for namespace isolation, node constraint is some kind of k8s = taints and tolerations. So to this Jira issue, to make up prefix for node attributes from different= =C2=A0 sources is a kind of namespace isolation.=C2=A0 For now,=C2=A0 # Centralized: attributes set by users (admin or normal users) can use a p= refix like {color:#FF0000}yarn_rm_admin/{color} # Distributed: attributes collected by a certain attribute provider on eac= h NM can use a prefix like {color:#FF0000}yarn_nm/{color} # System: some built-in attributes in yarn, set by yarn internal component= s, e.g scheduler like {color:#FF0000}yarn_system/{color} then, In RM merge from these sources, no need to handle the conflict cases. In placement constraints for node attributes should specify prefix to=C2=A0= indicate the sources/namespaces, or use yarn_nm/ prefix by default. [~cheersyang] [~leftnoteasy] [~Naganarasimha]=C2=A0 any comment?=C2=A0 Than= ks. > Attach prefixes to different type of node attributes > ---------------------------------------------------- > > Key: YARN-7854 > URL: https://issues.apache.org/jira/browse/YARN-7854 > Project: Hadoop YARN > Issue Type: Sub-task > Components: RM > Reporter: Weiwei Yang > Assignee: LiangYe > Priority: Major > > There are multiple types of node attributes depending on which source it = comes from, includes > # Centralized: attributes set by users (admin or normal users) > # Distributed: attributes collected by a certain attribute provider on e= ach NM > # System: some built-in attributes in yarn, set by yarn internal compone= nts, e.g scheduler > To better manage these attributes, we introduce the prefix (namespace) co= ncept to the an attribute. This Jira is opened to figure out how to attach = prefixes (automatically/implicitly or explicitly) to different type of attr= ibutes. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: yarn-issues-help@hadoop.apache.org