ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim Thorpe (JIRA)" <>
Subject [jira] [Issue Comment Deleted] (AMBARI-15388) Custom services need a way to integrate in the upgrade process
Date Wed, 18 May 2016 13:23:12 GMT


Tim Thorpe updated AMBARI-15388:
    Comment: was deleted

(was: I added a design doc and created a review board request.  

There are two ways to make these changes, the alternate approach would be to only make the
java changes and not split the upgrade xml files.  This would still allow new services to
add themselves into the upgrade.  The benefit of this is that for the stack services you only
have one upgrade xml file.  The problem with that is it is easier for a particular service
to have unintentional changes between upgrade xml files.  Variations on how a service upgrades
get hidden in the huge upgrade xml files.)

> Custom services need a way to integrate in the upgrade process
> --------------------------------------------------------------
>                 Key: AMBARI-15388
>                 URL:
>             Project: Ambari
>          Issue Type: Improvement
>          Components: ambari-server
>    Affects Versions: trunk
>            Reporter: Tim Thorpe
>            Assignee: Tim Thorpe
>             Fix For: trunk
>         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

View raw message