ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xi Wang (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-13393) Express Upgrade: UX changes for upgrade method selections window
Date Tue, 13 Oct 2015 22:49:05 GMT

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

Xi Wang updated AMBARI-13393:
-----------------------------
    Description: 
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".


  was:
UI for stack upgrade needs to present the user with two different upgrade methods: Rolling
Upgrade, Stop-and-Start 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 "Stop-and-Start Upgrade".



> 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
>
>
> 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)

Mime
View raw message