Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Fri, 20 May 2016 18:47:12 +0000 (UTC)
From: "Tim Thorpe (JIRA)" <jira@apache.org>
To: issues@ambari.apache.org
Message-ID: <JIRA.12949232.1457714782000.251930.1463770032993@Atlassian.JIRA>
In-Reply-To: <JIRA.12949232.1457714782000@Atlassian.JIRA>
References: <JIRA.12949232.1457714782000@Atlassian.JIRA> <JIRA.12949232.1457714782542@arcas>
Subject: [jira] [Updated] (AMBARI-15388) Custom services need a way to
 integrate in the upgrade process
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 20 May 2016 18:47:14 -0000


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

Tim Thorpe updated AMBARI-15388:
--------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

> Custom services need a way to integrate in the upgrade process
> --------------------------------------------------------------
>
>                 Key: AMBARI-15388
>                 URL: https://issues.apache.org/jira/browse/AMBARI-15388
>             Project: Ambari
>          Issue Type: Improvement
>          Components: ambari-server
>    Affects Versions: trunk
>            Reporter: Tim Thorpe
>            Assignee: Tim Thorpe
>             Fix For: trunk, 2.4.0
>
>         Attachments: AMBARI-15388 Design.pdf, AMBARI-15388.patch
>
>   Original Estimate: 336h
>  Remaining Estimate: 336h
>
> Currently the upgrade is defined as a series of xml files specific to the current stack version and the target stack version.  Each upgrade xml defines the overall sequence of the upgrade and what needs to be done for each service.  Custom services need to be able to specify their upgrade process and how those steps fit into the upgrade process.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)