Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Wed, 29 Oct 2014 16:26:35 +0000 (UTC)
From: "Robert Nettleton (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12751419.1414599964000.363960.1414599995858@Atlassian.JIRA>
In-Reply-To: <JIRA.12751419.1414599964000@Atlassian.JIRA>
References: <JIRA.12751419.1414599964000@Atlassian.JIRA>
 <JIRA.12751419.1414599964187@arcas>
Subject: [jira] [Created] (AMBARI-8021) Hostname information included in
 Blueprint export for HDP 2.2 cluster
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Robert Nettleton created AMBARI-8021:
----------------------------------------

             Summary: Hostname information included in Blueprint export for HDP 2.2 cluster
                 Key: AMBARI-8021
                 URL: https://issues.apache.org/jira/browse/AMBARI-8021
             Project: Ambari
          Issue Type: Bug
          Components: ambari-server
    Affects Versions: 1.7.0
            Reporter: Robert Nettleton
            Assignee: Robert Nettleton
             Fix For: 1.7.0


After launching an HDP 2.2 cluster using the Ambari UI, a Blueprint exported from the cluster will include hostname information for the following properties:

1. Hostname info appears after security is enabled (Knox also deployed in cluster): 

core-site : "hadoop.proxyuser.knox.hosts"
webhcat-site: "webhcat.proxyuser.knox.hosts"
oozie-site: "hadoop.proxyuser.knox.hosts"

2. kafka-broker: "kafka.ganglia.metrics.host"

3. yarn-site: "hadoop.registry.zk.quorum"
   slider-client: "slider.zookeeper.quorum"
   kafka-broker: "zookeeper.connect"

The Knox-related properties only appear in the exported Blueprint when Knox and Security are enabled, but the other properties appear when the various services are deployed in either case (Slider, Kafka, Yarn). 

The Blueprint configuration processor needs to be updated to account for these new properties in the HDP 2.2 stack. 

I'm working on a patch for this, and will be submitting it shortly. 


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)