[
https://issues.apache.org/jira/browse/AMBARI-23205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley resolved AMBARI-23205.
--------------------------------------
Resolution: Fixed
> Refactor host_version Tracking for MPacks
> -----------------------------------------
>
> Key: AMBARI-23205
> URL: https://issues.apache.org/jira/browse/AMBARI-23205
> Project: Ambari
> Issue Type: Task
> Affects Versions: 3.0.0
> Reporter: Jonathan Hurley
> Assignee: Jonathan Hurley
> Priority: Critical
> Labels: pull-request-available
> Fix For: 3.0.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> 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).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
