You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ambari.apache.org by "Sumit Mohanty (JIRA)" <ji...@apache.org> on 2013/04/04 18:51:15 UTC

[jira] [Resolved] (AMBARI-1424) Upgrade Ambari for 1.3.0

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

Sumit Mohanty resolved AMBARI-1424.
-----------------------------------

    Resolution: Fixed
    
> Upgrade Ambari for 1.3.0
> ------------------------
>
>                 Key: AMBARI-1424
>                 URL: https://issues.apache.org/jira/browse/AMBARI-1424
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: 1.3.0
>            Reporter: Sumit Mohanty
>            Assignee: Sumit Mohanty
>             Fix For: 1.3.0
>
>         Attachments: AMBARI-1424.patch
>
>   Original Estimate: 144h
>  Remaining Estimate: 144h
>
> * Modify upgrade to not overwrite configuration files (e.g. ambari-agent.ini). Upgrade or a pre-install script will save the configurations. A post-install script will restore the configuration file.
> * -Refactor RPM packages such that ambari can be managed as ambari\* removing the need to separately install/upgrade server agents etc.-
> * Ambari upgrade ddl script
> ** Create a table to store Ambari metadata such as version information
> * Modify Ambari Server to check version in the store and fail start if its not greater than desired

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira