[
https://issues.apache.org/jira/browse/AMBARI-21430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16079550#comment-16079550
]
Hudson commented on AMBARI-21430:
---------------------------------
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #7742 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/7742/])
AMBARI-21430. Allow Multiple Versions of Stack Tools to Co-Exist - fix
(adoroszlai:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=d0f7a51537469740e5397486b1e2c19862c26c01])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog252.java
> Allow Multiple Versions of Stack Tools to Co-Exist
> --------------------------------------------------
>
> Key: AMBARI-21430
> URL: https://issues.apache.org/jira/browse/AMBARI-21430
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.5.2
> Reporter: Jonathan Hurley
> Assignee: Jonathan Hurley
> Priority: Blocker
> Fix For: 2.5.2
>
> Attachments: AMBARI-21430.patch
>
>
> Currently, the stack tools:
> - {{cluster-env/stack_features}}
> - {{cluster-env/stack_tools}}
> - {{cluster-env/stack_root}}
> Are bound to the {{cluster-env}} without any sort of scoping. This prevents 2
> sets of stack tools from co-existing. Although Ambari doesn't support more
> than a single stack in 2.x, we do support upgrades from one stack vendor to
> another. Therefore, we need this support to send the right tools on the
> commands.
> This will involve the following work:
> - Changing the existing stack tools/features/root to have a stack name as the
> key in the JSON
> - Altering the existing {{cluster-env}} tools on upgrade
> - Ensuring that the stack tools/features for a repository's stack exist when
> distributing that stack
> - Changing any Python code which references the stack tools (stack_tools.py,
> alerts, etc)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
