ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rishi Pidva (JIRA)" <>
Subject [jira] [Commented] (AMBARI-8166) Implement custom command for checking connectivity to KDC, via REST API
Date Fri, 05 Dec 2014 21:10:14 GMT


Rishi Pidva commented on AMBARI-8166:

[~jaimin], [~rlevas] -- a follow-up question. In terms of workflow, is our assumption that
this point KDC server has already been setup and it's up and running (i.e. listening on KDC
port)? If yes, why do we have external AD/KDC details on this screen? Are we going to modify
the configuration of that KDC? If no, then cluster hosts will not be able to connect to specified
KDC host on specified port.

> 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