ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <>
Subject [jira] [Commented] (AMBARI-18888) Ambari-agent: Create configuration files with JCEKS information
Date Wed, 30 Nov 2016 06:14:58 GMT


Hadoop QA commented on AMBARI-18888:

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 1 new or modified
test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number
of release audit warnings.

    {color:red}-1 core tests{color}.  The patch failed these unit tests in ambari-server:


Test results:
Console output:

This message is automatically generated.

> Ambari-agent: Create configuration files with JCEKS information
> ---------------------------------------------------------------
>                 Key: AMBARI-18888
>                 URL:
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-agent
>            Reporter: Nahappan Somasundaram
>            Assignee: Nahappan Somasundaram
>         Attachments: rb53747.patch
> When a non-status command is received, a command.json file is generated. This file contains
the passwords used in a configuration. When the command is then executed, ambari agent spawns
off a subprocess to execute component-specific Python scripts to generate the configuration
files using the data from the command.json file.
> To avoid storing clear text passwords in command.json file and configuration files, ambari-agent
will first generate the JCEKS files corresponding to the configuration information in the
command JSON blob coming from the server and then generate the command.json with the path
to the JCEKS store instead of clear text passwords for *password* properties.
> Subsequently when executing a command, ambari-agent will generate the configuration files
with the JCEKS path information from command.json.

This message was sent by Atlassian JIRA

View raw message