[
https://issues.apache.org/jira/browse/AMBARI-15388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15206967#comment-15206967
]
Tim Thorpe commented on AMBARI-15388:
-------------------------------------
The patch file still stands. I know there are a some changes that will be
required, first to update it such that it can be successfully patched (it was
quite a few days old when the process was attempted). Secondly I need to make
sure the service check section is ordered (based on Nate's comment).
> 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 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. 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)
