You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ambari.apache.org by "Tim Thorpe (JIRA)" <ji...@apache.org> on 2016/03/11 20:20:39 UTC

[jira] [Updated] (AMBARI-15388) Upgrade XML should be pushed down as much as possible to the services

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

Tim Thorpe updated AMBARI-15388:
--------------------------------
    Attachment: AMBARI-15388.patch

Patch splitting the upgrade xml.

> Upgrade XML should be pushed down as much as possible to the services
> ---------------------------------------------------------------------
>
>                 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
>
>         Attachments: 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.  It would both easier to maintain and easier to add new services, if the services themselves could specify what should be done during their upgrade.



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