[AMBARI-23569] Provide Mpack Package Name to Install in metainfo.xml

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0.0
• Fix Version/s: 3.0.0
• Component/s: ambari-server
• Labels: pull-request-available
• Assignee: Madhuvanthi Radhakrishnan
• Reporter: Madhuvanthi Radhakrishnan
• Created: 12/Apr/18 21:46
• Updated: 16/Apr/18 18:07
• Resolved: 16/Apr/18 18:07

Description

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).

Issue Links

• links to: GitHub Pull Request #1009