ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Di Li (JIRA)" <>
Subject [jira] [Updated] (AMBARI-18962) Make check_package_condition in overridable by services in stacks
Date Tue, 22 Nov 2016 19:39:58 GMT


Di Li updated AMBARI-18962:
    Attachment: AMBARI-18962.patch

> Make check_package_condition in overridable by services in stacks
> ---------------------------------------------------------------------------
>                 Key: AMBARI-18962
>                 URL:
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: trunk, 2.5.0
>            Reporter: Di Li
>            Assignee: Di Li
>         Attachments: AMBARI-18962.patch
> check_package_condition method in was added via AMBARI-14739 to make the conditionally
installing RPMs controlled jointly by metainfo.xml and functions defined in
 For example, with the following metainfo.xml section. The has the should_install_ams_collector
function implementation.
>             <package>
>               <name>ambari-metrics-collector</name>
>               <skipUpgrade>true</skipUpgrade>
>               <condition>should_install_ams_collector</condition>
>             </package>
> The issue is that this is not easily extendable by services extensions (installed via
mpack), as any third party service needs to add functions to in resource_management
> This JIRA proposes to make check_package_condition overwritable at the service level
( by changing it from a static method to a instance method).
> Then each service can still maintain the metainfo.xml section, while implement its own
check_package_condition that pulls in its own package_condition util.

This message was sent by Atlassian JIRA

View raw message