[AMBARI-23205] Refactor host_version Tracking for MPacks

• Type: Task
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 3.0.0
• Fix Version/s: 3.0.0
• Labels: pull-request-available
• Epic Link: Management Packs: Repository Version Refactor
• Assignee: Jonathan Hurley
• Reporter: Jonathan Hurley
• Created: 12/Mar/18 15:00
• Updated: 15/Mar/18 14:31
• Resolved: 15/Mar/18 14:31

Description

As part of the ongoing effort to remove repository version, the ability to track installation of management packs must change as well. We previously were tracking the installation of a repository on every host, marking it as OUT_OF_SYNC, CURRENT, etc, depending on the state.

With management pack meta-RPMs, things get quite a bit easier. We no longer have to worry about specific versions being reported back per install nor do we need to worry about per-component installation states. Instead, there is only the need to track which mpacks have been installed on a given host.

This also allows us to simplify the states that we track. The proposal is to track the following states:

• NOT_REQUIRED
• NOT_INSTALLED
• INSTALLING
• INSTAL_FAILED
• INSTALLED

The NOT_REQUIRED state might actually not be needed. It's going to depend on how what queries might be needed to retrieve information about service groups (and their associated mpacks).

Issue Links

• links to: GitHub Pull Request #628