You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/10/04 20:40:00 UTC

[jira] [Updated] (AMBARI-24737) Expose Upgrade Check Classes via an Ambari Client Library

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

ASF GitHub Bot updated AMBARI-24737:
------------------------------------
    Labels: pull-request-available  (was: )

> Expose Upgrade Check Classes via an Ambari Client Library
> ---------------------------------------------------------
>
>                 Key: AMBARI-24737
>                 URL: https://issues.apache.org/jira/browse/AMBARI-24737
>             Project: Ambari
>          Issue Type: Task
>    Affects Versions: 2.8.0
>            Reporter: Jonathan Hurley
>            Assignee: Jonathan Hurley
>            Priority: Critical
>              Labels: pull-request-available
>             Fix For: 2.8.0
>
>
> The pre-upgrade check framework inside of Ambari needs to be migrated to the Ambari API/SPI being developed as part of AMBARI-24685 so that 3rd party stack developers can use this to compile and deliver their own custom upgrade checks for their stack.
> The following items should be included:
> - A way to obtain configuration information about the cluster's services
> - Topology information, including services installed and the components/hosts of the cluster
> The existing checks which are not stack-specific should remain in Apache and altered to use the new framework. This means that the {{ambari-server}} project will have a dependency on the new module created as part of AMBARI-24685.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)