ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Levas (JIRA)" <>
Subject [jira] [Commented] (AMBARI-8166) Implement custom command for checking connectivity to KDC, via REST API
Date Mon, 08 Dec 2014 15:16:13 GMT


Robert Levas commented on AMBARI-8166:

[~rpidva], At the point when the test is to be invoked, it is expected that the external KDC/AD
has already been set up and is running.  We need the details on this screen to pass back to
the Ambari server to use to build the {{krb5.conf}} files on the Kerberos client machines
in the cluster - which should be all of the hosts in the cluster. It is unlikely that we would
be able to update the KDC/AD settings from the Ambari service, so the data is only for cluster

> Implement custom command for checking connectivity to KDC, via REST API
> -----------------------------------------------------------------------
>                 Key: AMBARI-8166
>                 URL:
>             Project: Ambari
>          Issue Type: New Feature
>          Components: ambari-agent, ambari-server
>    Affects Versions: 2.0.0
>            Reporter: Robert Levas
>            Assignee: Rishi Pidva
>              Labels: connectivity_, kdc, kerberos
>         Attachments: Screen Shot 2014-11-04 at 11.16.41 PM.png
> There needs to be a way, given the details about a KDC to verify that Ambari and (optionally)
the nodes in the existing cluster can connect to it. 
> From the cluster hosts, this test should test that the address and port combinations
are reachable. 
> From the Ambari server, this test should make sure the administrator credentials allow
at least read access to the KDC.
> As an example of a similar action, see how Oozie does this for DB check pre install.

This message was sent by Atlassian JIRA

View raw message