ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nate Cole (JIRA)" <>
Subject [jira] [Commented] (AMBARI-10472) RU: add compatible stacks for upgrade purposes
Date Wed, 15 Apr 2015 11:52:58 GMT


Nate Cole commented on AMBARI-10472:

You may be confusing the purpose of this JIRA.  Consider the following use case.
* User has installed Ambari 2.0 and stack HDP-2.2.x.
* Rolling Upgrades (of the stack) allows you to go from HDP-2.2.x to HDP-2.2.y.  You do this
by creating a stack repo version for HDP-2.2.y.
* Now, if you create a repo version for, say, HDP-2.3, that will get saved to the database.

The issue becomes, in the UI, that when you are showing the list of stacks to upgrade to -
it will only use the current cluster's stack version.  The fix (this JIRA) is to add an endpoint
that will show you the list of compatible stacks that you can upgrade to.  A cluster with
HDP-2.2 should show you all other HDP-2.2.* and HDP-2.3* stacks.  You are right in one sense,
we have a tightly coupled mechanism to do that - on purpose.  It's not the goal of this JIRA
to design how we do stack management, rather to indicate valid upgrade paths for a deployed

> RU: add compatible stacks for upgrade purposes
> ----------------------------------------------
>                 Key: AMBARI-10472
>                 URL:
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-server
>            Reporter: Nate Cole
>            Assignee: Nate Cole
>             Fix For: 2.1.0
>         Attachments: AMBARI-10472.patch
> Changes required to support adding cross-stack versions and installation for a cluster.

This message was sent by Atlassian JIRA

View raw message