ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim Thorpe (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-15388) Custom services need a way to integrate in the upgrade process
Date Wed, 06 Apr 2016 20:29:25 GMT

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

Tim Thorpe updated AMBARI-15388:
--------------------------------
    Description: 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.
 (was: 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.)

> Custom services need a way to integrate in the upgrade process
> --------------------------------------------------------------
>
>                 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.  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
(v6.3.4#6332)

Mime
View raw message