[
https://issues.apache.org/jira/browse/AMBARI-12915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14718635#comment-14718635
]
Sumit Mohanty commented on AMBARI-12915:
----------------------------------------
Makes sense. For backward compatibility, I assume, by default this property
will not be part of the .ini file. What will be the order of precedence if this
property and the scripts are specified.
One issue is that it will force config files to be different on each host and
will be an added complexity for IT if they want to go this route.
> 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)
