You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Jonathan Hurley (JIRA)" <ji...@apache.org> on 2017/07/07 15:43:00 UTC

[jira] [Created] (AMBARI-21430) Allow Multiple Versions of Stack Tools to Co-Exist

Jonathan Hurley created AMBARI-21430:
----------------------------------------

             Summary: 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


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)