You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Nahappan Somasundaram (JIRA)" <ji...@apache.org> on 2016/04/22 02:47:12 UTC

[jira] [Updated] (AMBARI-16030) Ambari version history: Add ambari_version_history table for record keeping history of ambari versions

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

Nahappan Somasundaram updated AMBARI-16030:
-------------------------------------------
    Description: 
When investigating customer issues, information about history about Ambari versions is missing. We rely on this information to be provided in the EAR. Many times information in the EAR is inaccurate. Also information about when the Ambari upgrades actually happened in the past is completely missing. 

Instead of relying on this information to be provided, Ambari should record Ambari upgrade history in Ambari DB. 

{noformat}
ambari_version_history
Version                    Date                                    Notes
2.2.2.0-1            02/09/2015 01:00:00                Clean Install
2.2.3.0-2            03/10/2015 01:00:00                Upgraded 2.2.2.0-1 -> 2.2.3.0-2
2.4.0.0-3            06/09/2015 01:00:00                Upgraded 2.2.3.0-2 -> 2.4.0.0-3
{noformat}


  was:
When investigating customer issues, information about history about Ambari versions is missing. We rely on this information to be provided in the EAR. Many times information in the EAR is inaccurate. Also information about when the Ambari upgrades actually happened in the past is completely missing. 

Instead of relying on this information to be provided, Ambari should record Ambari upgrade history in Ambari DB. 

{noformat}
ambari_version_history
Version                    Date                                    Notes
2.2.2.0-1            02/09/2015 01:00:00                Clean Install
2.2.3.0-2            03/10/2015 01:00:00                Upgraded 2.2.2.0-1 -> 2.2.3.0-2
2.4.0.0-3            06/09/2015 01:00:00                Upgraded 2.2.3.0-2 -> 2.4.0.0-3
{noformat}

cc: [~mahadev] [~smohanty] [~swagle]

Design document: https://docs.google.com/a/hortonworks.com/document/d/1RcAth8M1oEDOjIZ0qMaCAtatCyz6qdLWuEcZLC4Ejbs/edit?usp=sharing


> Ambari version history: Add ambari_version_history table for record keeping history of ambari versions
> ------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-16030
>                 URL: https://issues.apache.org/jira/browse/AMBARI-16030
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-server
>    Affects Versions: 2.4.0
>            Reporter: Nahappan Somasundaram
>            Assignee: Nahappan Somasundaram
>             Fix For: 2.4.0
>
>
> When investigating customer issues, information about history about Ambari versions is missing. We rely on this information to be provided in the EAR. Many times information in the EAR is inaccurate. Also information about when the Ambari upgrades actually happened in the past is completely missing. 
> Instead of relying on this information to be provided, Ambari should record Ambari upgrade history in Ambari DB. 
> {noformat}
> ambari_version_history
> Version                    Date                                    Notes
> 2.2.2.0-1            02/09/2015 01:00:00                Clean Install
> 2.2.3.0-2            03/10/2015 01:00:00                Upgraded 2.2.2.0-1 -> 2.2.3.0-2
> 2.4.0.0-3            06/09/2015 01:00:00                Upgraded 2.2.3.0-2 -> 2.4.0.0-3
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)