Return-Path: X-Original-To: apmail-ambari-dev-archive@www.apache.org Delivered-To: apmail-ambari-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 6E2D110A55 for ; Wed, 31 Dec 2014 03:25:13 +0000 (UTC) Received: (qmail 60914 invoked by uid 500); 31 Dec 2014 03:25:13 -0000 Delivered-To: apmail-ambari-dev-archive@ambari.apache.org Received: (qmail 60815 invoked by uid 500); 31 Dec 2014 03:25:13 -0000 Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ambari.apache.org Delivered-To: mailing list dev@ambari.apache.org Received: (qmail 60796 invoked by uid 99); 31 Dec 2014 03:25:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 31 Dec 2014 03:25:13 +0000 Date: Wed, 31 Dec 2014 03:25:13 +0000 (UTC) From: "Hadoop QA (JIRA)" To: dev@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AMBARI-8479) YARN service components should indicate security state 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/AMBARI-8479?page=3Dcom.atlassia= n.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D142= 61853#comment-14261853 ]=20 Hadoop QA commented on AMBARI-8479: ----------------------------------- {color:green}+1 overall{color}. Here are the results of testing the latest= attachment=20 http://issues.apache.org/jira/secure/attachment/12689621/AMBARI-8479_02.p= atch against trunk revision . {color:green}+1 @author{color}. The patch does not contain any @author= tags. {color:green}+1 tests included{color}. The patch appears to include 2 = new or modified test files. {color:green}+1 javac{color}. The applied patch does not increase the = total number of javac compiler warnings. {color:green}+1 release audit{color}. The applied patch does not incre= ase the total number of release audit warnings. {color:green}+1 core tests{color}. The patch passed unit tests in amba= ri-server. Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/1130//t= estReport/ Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/1130/= /console This message is automatically generated. > YARN service components should indicate security state > ------------------------------------------------------ > > Key: AMBARI-8479 > URL: https://issues.apache.org/jira/browse/AMBARI-8479 > Project: Ambari > Issue Type: Improvement > Components: ambari-server, stacks > Affects Versions: 2.0.0 > Reporter: Robert Levas > Assignee: Robert Levas > Labels: kerberos, lifecycle, security > Fix For: 2.0.0 > > Attachments: AMBARI-8479_01.patch, AMBARI-8479_02.patch > > > The YARN service components should indicate security state when queried b= y Ambari Agent via STATUS_COMMAND. Each component should determine it's st= ate as follows: > h3. RESOURCEMANAGER > h4. Indicators > * Command JSON > ** config\['configurations']\['cluster-env']\['security_enabled']=20 > *** =3D =E2=80=9Ctrue=E2=80=9D > * Configuration File: /etc/hadoop/conf/yarn-site.xml > ** yarn.timeline-service.enabled > *** =3D "true" > *** required > ** yarn.timeline-service.http-authentication.type > *** =3D "kerberos" > *** required > ** yarn.acl.enable > *** =3D "true" > *** required > ** yarn.resourcemanager.keytab > *** not empty > *** path exists and is readable > *** required > ** yarn.resourcemanager.principal > *** not empty > *** required > ** yarn.resourcemanager.webapp.spnego-keytab-file > *** not empty > *** path exists and is readable > *** required > ** yarn.resourcemanager.webapp.spnego-principal > *** not empty > *** required > h4. Pseudocode > {code} > if indicators imply security is on and validate > if kinit(resourcemanager principal) succeeds > state =3D SECURED_KERBEROS > else > state =3D ERROR=20 > else > state =3D UNSECURED > {code} > h3. NODEMANAGER > h4. Indicators > * Command JSON > ** config\['configurations']\['cluster-env']\['security_enabled']=20 > *** =3D =E2=80=9Ctrue=E2=80=9D > * Configuration File: /etc/hadoop/conf/yarn-site.xml > ** yarn.timeline-service.enabled > *** =3D "true" > *** required > ** yarn.timeline-service.http-authentication.type > *** =3D "kerberos" > *** required > ** yarn.acl.enable > *** =3D "true" > *** required > ** yarn.nodemanager.keytab > *** not empty > *** path exists and is readable > *** required > ** yarn.nodemanager.principal > *** not empty > *** required > ** yarn.nodemanager.webapp.spnego-keytab-file > *** not empty > *** path exists and is readable > *** required > ** yarn.nodemanager.webapp.spnego-principal > *** not empty > *** required > h4. Pseudocode > {code} > if indicators imply security is on and validate > if kinit(nodemanager principal) succeeds > state =3D SECURED_KERBEROS > else > state =3D ERROR=20 > else > state =3D UNSECURED > {code} > h3. APP_TIMELINE_SERVER > h4. Indicators > * Command JSON > ** config\['configurations']\['cluster-env']\['security_enabled']=20 > *** =3D =E2=80=9Ctrue=E2=80=9D > * Configuration File: /etc/hadoop/conf/yarn-site.xml > ** yarn.timeline-service.enabled > *** =3D "true" > *** required > ** yarn.timeline-service.http-authentication.type > *** =3D "kerberos" > *** required > ** yarn.acl.enable > *** =3D "true" > *** required > ** yarn.timeline-service.keytab > *** not empty > *** path exists and is readable > *** required > ** yarn.timeline-service.principal > *** not empty > *** required > ** yarn.timeline-service.http-authentication.kerberos.keytab > *** not empty > *** path exists and is readable > *** required > ** yarn.timeline-service.http-authentication.kerberos.principal > *** not empty > *** required > h4. Pseudocode > {code} > if indicators imply security is on and validate > if kinit(nodemanager principal) succeeds > state =3D SECURED_KERBEROS > else > state =3D ERROR=20 > else > state =3D UNSECURED > {code} > _*Note*_: Due to the _cost_ of calling {{kinit}} results should be cached= for a period of time before retrying. This may be an issue depending on t= he frequency of the heartbeat timeout. > _*Note*_: {{kinit}} calls should specify a _temporary_ cache file which s= hould be destroyed after command is executed - BUG-29477 -- This message was sent by Atlassian JIRA (v6.3.4#6332)