[
https://issues.apache.org/jira/browse/AMBARI-14567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15086018#comment-15086018
]
Hadoop QA commented on AMBARI-14567:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12780772/AMBARI-14567.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{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:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/4794//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/4794//console
This message is automatically generated.
> pluggable-stack script is not configurable (Can not deploy ambari with custom
> stack correctly, with out specific repos files for services)
> ------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AMBARI-14567
> URL: https://issues.apache.org/jira/browse/AMBARI-14567
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.2.0
> Reporter: Dmitry Lysnichenko
> Assignee: Dmitry Lysnichenko
> Fix For: 2.2.1
>
> Attachments: AMBARI-14567.patch
>
>
> *Important, As I understand:*
> Originally pluggable-stack script was designed to do following:
> * replace stack name
> * replace versions in packages and code
> *But this script is not configurable.* For example, we can't change just
> stack name and version, package versions will be also changed.
> We need to refactor pluggable-stack script and define more config options to
> allow to configure which replacements we will perform.
> STR:
> 1) Clone ambari sources from repository
> 2) make
> {code}
> python
> /home/eugene/dev/ambari/ambari-common/src/main/python/pluggable_stack_definition/GenerateStackDefinition.py
> -c ${pluggableStackDefinitionConfig} -r ${resourcesSrcLocation} -o
> ${pluggableStackDefinitionOutput}
> {code}
> where
> {code}
> ${pluggableStackDefinitionConfig} - way to CUSTOM.json
> ${resourcesSrcLocation} = /ambari/ambari-server/src/main/resources
> ${pluggableStackDefinitionOutput} - some directory for output
> {code}
> 3) Put custom_stack_map.json to
> /ambari/ambari-common/src/main/python/pluggable_stack_definition/resources/CUSTOM
> 4) make
> {code}
> mvn versions:set -DnewVersion=2.1.3.0.0
> {code}
> for ambari and ambari-metrics
> 5) make packages
> {code}
> mvn -B clean package rpm:rpm -Dpython.ver="python >= 2.6" -DskipTests -pl
> ambari-agent,ambari-web,ambari-server,ambari-admin,ambari-views,ambari-metrics/ambari-metrics-common
> -Dstack.distribution=CUSTOM
> -DpluggableStackDefinitionConfig=/ambari/ambari-common/src/main/python/pluggable_stack_definition/configs/CUSTOM.json
> {code}
> 6) install and setup ambari from rpms
> 7) Try to deploy ambari
> *Actual results:*
> Can not deploy ambari with custom stack correctly, with out specific package
> files (3_3_*) for services.
> {code}
> resource_management.core.exceptions.Fail: Execution of '/usr/bin/yum -d 0 -e
> 0 -y install 'accumulo_3_3_*'' returned 1. Error: Nothing to do
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
