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 21DAC1866C for ; Fri, 28 Aug 2015 13:16:46 +0000 (UTC) Received: (qmail 55640 invoked by uid 500); 28 Aug 2015 13:16:45 -0000 Delivered-To: apmail-ambari-dev-archive@ambari.apache.org Received: (qmail 55605 invoked by uid 500); 28 Aug 2015 13:16:45 -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 55591 invoked by uid 99); 28 Aug 2015 13:16:45 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Aug 2015 13:16:45 +0000 Date: Fri, 28 Aug 2015 13:16:45 +0000 (UTC) From: "Greg Hill (JIRA)" To: dev@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AMBARI-12915) Make agent hostname configurable 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/AMBARI-12915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Greg Hill updated AMBARI-12915: ------------------------------- Description: Currently the agent can either get the hostname from the local system, or you can inject a script to tell it what hostname to use using the 'hostname_script' config value. I would like to add a 'hostname' config value to the agent section of the agent config so we can just tell the agent what hostname to use. The scenario this comes up in is that our Ambari setup uses a local DNS domain for internal traffic, but the Ambari API has a public FQDN that we use for the API. It would be much cleaner for us to just specify the hostname in the config rather than jumping through hoops to generate a script to use to derive it. https://github.com/apache/ambari/blob/087d9003ecf6af33890e4f48743d7237a30d6438/ambari-agent/src/main/python/ambari_agent/hostname.py#L40 was: Currently the agent can either get the hostname from the local system, or you can inject a script to tell it what hostname to use using the 'hostname_script' config value. I would like to add a 'hostname' config value to the agent section of the agent config so we can just tell the agent what hostname to use. The scenario this comes up in is that our Ambari setup uses a local DNS domain for internal traffic, but the Ambari API has a public FQDN that we use for the API. It would be much cleaner for us to just specify the hostname in the config rather than jumping through hoops to generate a script to use to derive it. > Make agent hostname configurable > -------------------------------- > > Key: AMBARI-12915 > URL: https://issues.apache.org/jira/browse/AMBARI-12915 > Project: Ambari > Issue Type: Improvement > Components: ambari-agent > Affects Versions: 2.1.0 > Reporter: Greg Hill > Assignee: Greg Hill > Priority: Minor > > Currently the agent can either get the hostname from the local system, or you can inject a script to tell it what hostname to use using the 'hostname_script' config value. I would like to add a 'hostname' config value to the agent section of the agent config so we can just tell the agent what hostname to use. > The scenario this comes up in is that our Ambari setup uses a local DNS domain for internal traffic, but the Ambari API has a public FQDN that we use for the API. It would be much cleaner for us to just specify the hostname in the config rather than jumping through hoops to generate a script to use to derive it. > https://github.com/apache/ambari/blob/087d9003ecf6af33890e4f48743d7237a30d6438/ambari-agent/src/main/python/ambari_agent/hostname.py#L40 -- This message was sent by Atlassian JIRA (v6.3.4#6332)