Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Thu, 19 Mar 2015 16:19:38 +0000 (UTC)
From: "Jayush Luniya (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12741395.1410757016000.145054.1426781978858@Atlassian.JIRA>
In-Reply-To: <JIRA.12741395.1410757016000@Atlassian.JIRA>
References: <JIRA.12741395.1410757016000@Atlassian.JIRA>
 <JIRA.12741395.1410757016756@arcas>
Subject: [jira] [Updated] (AMBARI-7301) Remove the ambri-web logic around
 stack version number
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jayush Luniya updated AMBARI-7301:
----------------------------------
    Fix Version/s:     (was: 2.0.0)
                   2.1.0

> Remove the ambri-web logic around stack version number
> ------------------------------------------------------
>
>                 Key: AMBARI-7301
>                 URL: https://issues.apache.org/jira/browse/AMBARI-7301
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-web
>    Affects Versions: 1.7.0
>            Reporter: Jaimin D Jetly
>            Assignee: Jaimin D Jetly
>             Fix For: 2.1.0
>
>
> Cardinality field can imply number of allowable service components in the cluster.
> If any master components has a static number greater than 1 (For example: 2), then we can infer that it supports high availability
> Although for other features (example: kerberos security, move master, metrics, alerts support) that are independent of any information provided in stack, I agree that Nate Cole proposal (done offline) of having feature will be helpful in such scenarios.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)