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/07/12 13:49:00 UTC

[jira] [Resolved] (AMBARI-24282) Report MPack Version on Start/Status

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

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

> Report MPack Version on Start/Status
> ------------------------------------
>
>                 Key: AMBARI-24282
>                 URL: https://issues.apache.org/jira/browse/AMBARI-24282
>             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: 0.5h
>  Remaining Estimate: 0h
>
> When components are installed or are started/restarted, they must report their versions back to Ambari server so that we can accurately track whether or not they are running the correct binaries. With the switch to mpacks, this means that {{stack-select}} is deprecated and must be replaced:
> - Add mpack version tracking to the SQL and java classes
> - Introduce a {{deprecated}} annotation and begin marking Python code dealing with stack tools as deprecated
> - Use the mpack instance manager to report versions
> - Change the structured output of the agent to report multiple possible results in a single payload
> - Handle incoming version changes and update the appropriate service component hosts.
> - Update the version alert to check for mpack versions



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