[
https://issues.apache.org/jira/browse/AMBARI-15388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15206961#comment-15206961
]
Tim Thorpe commented on AMBARI-15388:
-------------------------------------
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.
> 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)
