[
https://issues.apache.org/jira/browse/AMBARI-15388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15202235#comment-15202235
]
Alejandro Fernandez commented on AMBARI-15388:
----------------------------------------------
I agree about sending a design review to the community and the points mentioned
above. I completely agree that upgrade packs should be extensible to facilitate
adding other services. The reason why a single file exists today is because we
had to capture the order, prechecks, and of course other groups that are not
associated with any service but instead the Cluster.
If we do split it out, then a service should define its dependencies (or
references to other steps that must complete before). This model actually lends
itself to parallelizing groups such as say Atlas, Falcon, Storm.
> 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)
