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 9A16D18DE7 for ; Wed, 14 Oct 2015 03:46:06 +0000 (UTC) Received: (qmail 56406 invoked by uid 500); 14 Oct 2015 03:46:06 -0000 Delivered-To: apmail-ambari-dev-archive@ambari.apache.org Received: (qmail 56367 invoked by uid 500); 14 Oct 2015 03: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 56352 invoked by uid 99); 14 Oct 2015 03:46:06 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 14 Oct 2015 03:46:06 +0000 Date: Wed, 14 Oct 2015 03:46:06 +0000 (UTC) From: "Hudson (JIRA)" To: dev@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (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:comment-tabpanel&focusedCommentId=14956201#comment-14956201 ] Hudson commented on AMBARI-13393: --------------------------------- SUCCESS: Integrated in Ambari-trunk-Commit #3639 (See [https://builds.apache.org/job/Ambari-trunk-Commit/3639/]) AMBARI-13393. Express Upgrade: UX changes for upgrade method selections (xiwang: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=92915952abe64e390b5ec348abc0768746b8be7b]) * ambari-web/app/messages.js * ambari-web/app/styles/stack_versions.less * ambari-web/test/controllers/main/admin/stack_and_upgrade_controller_test.js * ambari-web/app/utils/ajax/ajax.js * ambari-web/app/templates/main/admin/stack_upgrade/stack_upgrade_wizard.hbs * ambari-web/app/views/common/modal_popups/cluster_check_popup.js * ambari-web/app/templates/main/admin/stack_upgrade/upgrade_options.hbs * ambari-web/app/routes/stack_upgrade_routes.js * ambari-web/app/controllers/main/admin/stack_and_upgrade_controller.js > 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.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)