[jira] [Commented] (AMBARI-12915) Make agent hostname configurable

["Robert Levas (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AMBARI-12915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15180118#comment-15180118 ] 

Robert Levas commented on AMBARI-12915:
---------------------------------------

*I think that this is a bad idea*...

When Kerberos is enabled on the cluster, the Hadoop services (as well as some other services like Oozie), internally perform a replacement on the {{_HOST}} value in principal names.  The  mechanism to do this is not getting the hostname value from the ambari-agent config or ambari-server command files. I assume if uses something that generates a hostname value like {{hostname -f}} by querying the network configuration. 

Because of this, there will be a disconnect between service principal names that ambari-agent scripts calculate and service principal names that Hadoop services generate.

Additionally, when it comes to validation of the principal names between hosts, a remote host will probably use DNS to determine the expected hostname and will have no clue about the faked named provided in the ambari-agent config file. 



> 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
>         Attachments: AMBARI-12915.patch
>
>
> 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)