ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rishi Pidva (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-8166) Implement custom command for checking connectivity to KDC, via REST API
Date Wed, 14 Jan 2015 06:45:34 GMT

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

Rishi Pidva updated AMBARI-8166:
--------------------------------
    Attachment: AMBARI-8166.patch.6

Accidentally removed properties init. Attaching new patch.

> Implement custom command for checking connectivity to KDC, via REST API
> -----------------------------------------------------------------------
>
>                 Key: AMBARI-8166
>                 URL: https://issues.apache.org/jira/browse/AMBARI-8166
>             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
>             Fix For: 2.0.0
>
>         Attachments: AMBARI-8166-v2.patch, AMBARI-8166-v3.patch, AMBARI-8166.patch, AMBARI-8166.patch.4,
AMBARI-8166.patch.5, AMBARI-8166.patch.6, 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
(v6.3.4#6332)

Mime
View raw message