You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Jonathan Hurley (JIRA)" <ji...@apache.org> on 2018/03/01 19:13:00 UTC

[jira] [Resolved] (AMBARI-23107) Deprecate Repo Versions And Start Tracking Repo OS's For MPacks

     [ https://issues.apache.org/jira/browse/AMBARI-23107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Hurley resolved AMBARI-23107.
--------------------------------------
    Resolution: Fixed

> Deprecate Repo Versions And Start Tracking Repo OS's For MPacks
> ---------------------------------------------------------------
>
>                 Key: AMBARI-23107
>                 URL: https://issues.apache.org/jira/browse/AMBARI-23107
>             Project: Ambari
>          Issue Type: Task
>    Affects Versions: 3.0.0
>            Reporter: Jonathan Hurley
>            Assignee: Jonathan Hurley
>            Priority: Blocker
>              Labels: pull-request-available
>             Fix For: 3.0.0
>
>          Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> Repository Versions are no longer going to be needed since a single repository now can contain multiple versions of a management pack and its RPMs. Since the {{mpack.json}} file contains all the necessary version information, we no longer need to keep track of reported versions coming from a repo. However, repository versions are very tightly coupled now and to remove them without having a working replacement would be quite difficult. This Jira covers the following work items:
> - Begin marking deprecated classes and methods related to removal of repo versions and host versions
> - Start tracking mpack installations on a per-host basis
> - Associate repository OS and definition entities with the management pack (instead of a repo version)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)