You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Newton Alex (JIRA)" <ji...@apache.org> on 2014/11/18 02:16:33 UTC

[jira] [Commented] (AMBARI-7804) Ambari Automated Cluster Upgrades

    [ https://issues.apache.org/jira/browse/AMBARI-7804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14215545#comment-14215545 ] 

Newton Alex commented on AMBARI-7804:
-------------------------------------

[~ncole@hortonworks.com] The mockups and designs mostly revolve around the availability of versioned rpms. Not sure if you have thought through screens for non-versioned distributions like BIGTOP ? Features like Downgrade might not work for non-versioned rpms. Will there be provisions to disable such features based on the stack?

> Ambari Automated Cluster Upgrades
> ---------------------------------
>
>                 Key: AMBARI-7804
>                 URL: https://issues.apache.org/jira/browse/AMBARI-7804
>             Project: Ambari
>          Issue Type: Epic
>            Reporter: Newton Alex
>            Assignee: Newton Alex
>         Attachments: Ambari+Cluster+Upgrade+Requirements.pdf, RollingUpgradeAmbariMockups.pdf, RollingUpgradeAmbariRequirements.pdf, RollingUpgradeAmbariTechDetails.pdf
>
>
> Ambari should have the ability to automatically upgrade the clusters it had deployed. It would be nice to have a wizard that leads the users step by step into upgrading the cluster with minimal manual steps.



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