Madhuvanthi Radhakrishnan updated AMBARI-23569:
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

> Provide Mpack Package Name to Install in metainfo.xml
> -----------------------------------------------------
>                 Key: AMBARI-23569
>                 URL: https://issues.apache.org/jira/browse/AMBARI-23569
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 3.0.0
>            Reporter: Madhuvanthi Radhakrishnan
>            Assignee: Madhuvanthi Radhakrishnan
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 3.0.0
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
> In order to support parallel installations of mpacks on a single host, Ambari 
> will be need to have the exact package name, including build number, of the 
> mpack to install. This is a direct translation of what Ambari 2.x does when 
> attempting to install multiple versions of a component.
> In the case of Ambari 2.x, there was no way to provide the package 
> information to Ambari beyond a wildcard, which caused problems if there were 
> 2 builds close to each other on the host. Because of this (and because Ambari 
> needed to discover the version being installed), we had to perform a lot of 
> fragile trickery with yum/apt-get and {{hdp-select}}(and other similar tools).
> The {{mpack.json}} file should provide this to us now. There are a few 
> caveats:
>  - If there are mutliple tarballs built (one for each OS), then we only need 
> to provide the package name.
>  - If there is only 1 tarball built, then the {{mpack.json}} must have a 
> package name listing for every OS family. This is to allow for the 
> differences between package managers (like hdpcore_3_0_0_0_b1 and 
> hdpcore-3-0-0-0-b2).

This message was sent by Atlassian JIRA

Reply via email to