Return-Path: X-Original-To: apmail-ambari-dev-archive@www.apache.org Delivered-To: apmail-ambari-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 53DFB18EB4 for ; Thu, 15 Oct 2015 19:46:11 +0000 (UTC) Received: (qmail 29068 invoked by uid 500); 15 Oct 2015 19:46:06 -0000 Delivered-To: apmail-ambari-dev-archive@ambari.apache.org Received: (qmail 28881 invoked by uid 500); 15 Oct 2015 19:46:06 -0000 Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ambari.apache.org Delivered-To: mailing list dev@ambari.apache.org Received: (qmail 28759 invoked by uid 99); 15 Oct 2015 19:46:06 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 Oct 2015 19:46:06 +0000 Date: Thu, 15 Oct 2015 19:46:06 +0000 (UTC) From: "Xi Wang (JIRA)" To: dev@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (AMBARI-13393) Express Upgrade: UX changes for upgrade method selections window MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AMBARI-13393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xi Wang resolved AMBARI-13393. ------------------------------ Resolution: Fixed 2nd patch committed to trunk and branch-2.1 > 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)