[
https://issues.apache.org/jira/browse/AMBARI-12915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15180133#comment-15180133
]
Greg Hill commented on AMBARI-12915:
------------------------------------
Sometimes you have hosts that have both a public fqdn (for the ambari-server UI
and API) and a local dns name (for internal cluster traffic over a private
network) and you want the agent to identify itself as one and the server as the
other, so the agent running on the ambari-server box needs to be able to
disambiguate. It would be up to the operator to use the matching hostname with
kerberos if they reconfigured the agent, since the default behavior is to rely
on the system hostname in both places. Our ambari server right now looks like
this:
ambari-$uuid.sub.domain.com - public IP with a valid SSL cert
ambari.local - local IP for agent traffic
The views rely on the system hostname to determine how to do API calls to the
ambari-server, so we have to make the system hostname be the public FQDN with
the valid cert or most of the views are broken.
The agent needs to use ambari.local as the hostname so that it converses over
the private, protected network, and all of our automation continues to work.
We use the hostname_script right now to spit out the expected 'ambari.local'
hostname for the agent, but just putting that directly in the config file
seemed cleaner. If we added kerberos, we would likely continue to use the
'ambari.local' hostname with it so it would work as expected.
I realize this isn't necessarily a common setup, but I didn't modify the
default behavior at all. If they configure a hostname it should be because
they know what they're doing. That's my $0.02
> 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)
