[
https://issues.apache.org/jira/browse/AMBARI-13393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14959456#comment-14959456
]
Yusaku Sako commented on AMBARI-13393:
--------------------------------------
+1 for the patch.
> Express Upgrade: UX changes for upgrade method selections window
> ----------------------------------------------------------------
>
> Key: AMBARI-13393
> URL: https://issues.apache.org/jira/browse/AMBARI-13393
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.2.0, 2.1.3
> Reporter: Xi Wang
> Assignee: Xi Wang
> Fix For: 2.2.0, 2.1.3
>
> Attachments: AMBARI-13393-2.patch, AMBARI-13393.patch
>
>
> UI for stack upgrade needs to present the user with two different upgrade
> methods: Rolling Upgrade, Express Upgrade.
> Today, the UI invokes the /upgrades API to begin the upgrade. This will need
> to pass in the type of upgrade as "rolling" or "nonrolling".
> The upgrade type will only be available if the stack version contains an
> upgrade pack for it.
> {code:title=POST api/v1/clusters/c1/upgrades}
> {
> "Upgrade": {
> "repository_version": "2.3.0.0-2545",
> "type": "NON-ROLLING"
> }
> }
> {code}
> Further, the Upgrade Wizard dialog box will need to change the title to
> reflect if it's a "Rolling Upgrade" or "Express Upgrade".
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
