You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Di Li (JIRA)" <ji...@apache.org> on 2017/06/27 20:56:00 UTC
[jira] [Commented] (AMBARI-21348) Provide the Ability for Ambari To
Upgrade From One Vendor's Stack To Another
[ https://issues.apache.org/jira/browse/AMBARI-21348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16065449#comment-16065449 ]
Di Li commented on AMBARI-21348:
--------------------------------
A related JIRA for branch-feature-AMBARI-21348 is https://issues.apache.org/jira/browse/AMBARI-21325 for the Ambari quicklink/Knox integration.
> Provide the Ability for Ambari To Upgrade From One Vendor's Stack To Another
> ----------------------------------------------------------------------------
>
> Key: AMBARI-21348
> URL: https://issues.apache.org/jira/browse/AMBARI-21348
> Project: Ambari
> Issue Type: Epic
> Affects Versions: 2.5.2
> Reporter: Jonathan Hurley
> Assignee: Jonathan Hurley
> Priority: Critical
> Fix For: 2.5.2
>
>
> Ambari currently cannot support full stack upgrades between stacks which have different names. For example, if you have FOO-1.0 installed and you want to upgrade to BAR-2.0, this is currently not possible. There are several top-level work items for this:
> - Removing assumptions about stack names when dealing with upgrades and creating commands
> - Allowing multiple stacks with different names to be registered and exposed via the web client
> - Providing an example stack which supports upgrades from a different vendor's stack
> - Support for stack tools on a per-stack basis.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)