ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Nettleton (JIRA)" <>
Subject [jira] [Updated] (AMBARI-16021) Update LogSearch integration to use configuration to obtain credential
Date Thu, 21 Apr 2016 19:02:25 GMT


Robert Nettleton updated AMBARI-16021:
    Attachment: AMBARI-16021.patch

Uploaded initial version of patch

> Update LogSearch integration to use configuration to obtain credential
> ----------------------------------------------------------------------
>                 Key: AMBARI-16021
>                 URL:
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.4.0
>            Reporter: Robert Nettleton
>            Assignee: Robert Nettleton
>            Priority: Critical
>             Fix For: 2.4.0
>         Attachments: AMBARI-16021.patch
> The LogSearch integration components in Ambari needs to obtain the credential used to
connect to the LogSearch service via a configuration mechanism.  
> In the initial checkins, the integration code used a hard-coded credential.  
> Now that AMBARI-15884 has implemented the stack and configuration support to allow a
user to configure the credential for the LogSearch Server, the Ambari Integration layer should
use this configuration, defined in:
> ambari/ambari-server/src/main/resources/common-services/LOGSEARCH/0.5.0/configuration/logsearch-admin-properties.xml
> This current JIRA tracks the work involved in updating the integration layer to obtain
the credential from the cluster's configuration, and use this credential to connect to the
LogSearch service.
> I'm working on a fix for this, and will be submitting a patch shortly. 

This message was sent by Atlassian JIRA

View raw message