[
https://issues.apache.org/jira/browse/AMBARI-12885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15294327#comment-15294327
]
Hadoop QA commented on AMBARI-12885:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12805275/AMBARI-12885.patch
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 36 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:
org.apache.ambari.server.upgrade.UpgradeCatalog240Test
org.apache.ambari.server.view.persistence.DataStoreImplTest
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/6922//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/6922//console
This message is automatically generated.
> Dynamic stack extensions - install and upgrade support for custom services
> --------------------------------------------------------------------------
>
> Key: AMBARI-12885
> URL: https://issues.apache.org/jira/browse/AMBARI-12885
> Project: Ambari
> Issue Type: New Feature
> Components: ambari-agent, ambari-server, ambari-web
> Reporter: Tim Thorpe
> Assignee: Tim Thorpe
> Attachments: AMBARI-12885.patch, Dynamic Stack Extensions - High
> Level Design v4.pdf
>
>
> The purpose of this proposal is to facilitate adding custom services to an
> existing stack. Ideally this would support adding and upgrading custom
> services separately from the core services defined in the stack. In
> particular we are looking at custom services that need to support several
> different stacks (different distributions of Ambari). The release cycle of
> the custom services may be different from that of the core stack; that is, a
> custom service may be upgraded at a different rate than the core distribution
> itself and may be upgraded multiple times within the lifespan of a single
> release of the core distribution.
> One possible approach to handling this would be dynamically extending a stack
> (after install time). It would be best to extend the stack in packages where
> a stack extension package can have one or more custom services.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
