ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Greg Hill (JIRA)" <>
Subject [jira] [Commented] (AMBARI-12915) Make agent hostname configurable
Date Fri, 28 Aug 2015 14:43:46 GMT


Greg Hill commented on AMBARI-12915:

Yeah, I was thinking it wouldn't be there by default.  You'd have to add it.  Precedence would

1. Config 'hostname', if it exists
2. Run config 'hostname_script', if it exists
3. Get system hostname

I agree that this wouldn't be ideal for everybody, but we can inject configs per node and
this would make it simpler for us.  I was planning on submitting a patch, but it'll probably
be next week before I can get to it.

> Make agent hostname configurable
> --------------------------------
>                 Key: AMBARI-12915
>                 URL:
>             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.

This message was sent by Atlassian JIRA

View raw message