You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Robert Levas (JIRA)" <ji...@apache.org> on 2015/03/06 18:52:38 UTC

[jira] [Updated] (AMBARI-9937) Ambari must support deployment on separate host

     [ https://issues.apache.org/jira/browse/AMBARI-9937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Levas updated AMBARI-9937:
---------------------------------
    Attachment: AMBARI-9937_trunk_01.patch

* Added kerberos.keytab.cache.dir to ambari.properties
* Added kerberos.keytab.cache.dir and default value (via erberosKeytabCacheDir property) to {{org.apache.ambari.server.configuration.Configuration}}
* Added "cachable" value to Kerberos keytab descriptor (default = true) to mark a keytab as being cachable or not
* Updated org.apache.ambari.server.serveraction.kerberos.CreateKeytabFilesServerAction to add to or use from the keytab cache as necessary
* Added explicit server specification in kadmin call to help with scenarios where the krb5.conf file isn't configured on the Ambari server
* Moved kdc_host and admin_server_host configuration properties from krb5-conf to kerberos-env
* Simplified krb5-conf by removing unnecessary properties that can be set in the template

Patch File [^AMBARI-9937_trunk_01.patch]

> Ambari must support deployment on separate host
> -----------------------------------------------
>
>                 Key: AMBARI-9937
>                 URL: https://issues.apache.org/jira/browse/AMBARI-9937
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.0.0
>            Reporter: Robert Levas
>            Assignee: Robert Levas
>            Priority: Critical
>              Labels: kerberos
>             Fix For: 2.0.0
>
>         Attachments: AMBARI-9937_trunk_01.patch
>
>
> It should be possible to deploy Ambari on a host that does not include any other services.
> The primary issue is that Ambari needs to be able to distribute keytabs to other hosts even if Ambari-Server is not running on a host with services that would otherwise have forced the Ambari-Server to be included in the keytab distribution process.
> To be clear, the following use case should be supported:
> * The Ambari-Server is deployed on a host with no other services 
> ** Other services are deployed on hosts separate from Ambari-Server
> * addHost should be possible



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)