Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Fri, 9 Sep 2016 19:53:20 +0000 (UTC)
From: "Robert Levas (JIRA)" <jira@apache.org>
To: issues@ambari.apache.org
Message-ID: <JIRA.13003956.1473450641000.534828.1473450800592@Atlassian.JIRA>
In-Reply-To: <JIRA.13003956.1473450641000@Atlassian.JIRA>
References: <JIRA.13003956.1473450641000@Atlassian.JIRA> <JIRA.13003956.1473450641548@arcas>
Subject: [jira] [Updated] (AMBARI-18352) Enhance the ability to compute
 whether an execute-stage should be included in the stack upgrade/downgrade
 work flow
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 09 Sep 2016 19:53:22 -0000


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

Robert Levas updated AMBARI-18352:
----------------------------------
    Summary: Enhance the ability to compute whether an execute-stage should be included in the stack upgrade/downgrade work flow  (was: Enhanced the ability to compute whether an execute-stage should be included in the stack upgrade/downgrade work flow)

> Enhance the ability to compute whether an execute-stage should be included in the stack upgrade/downgrade work flow
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-18352
>                 URL: https://issues.apache.org/jira/browse/AMBARI-18352
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-server
>    Affects Versions: 2.4.1
>            Reporter: Robert Levas
>            Assignee: Nate Cole
>             Fix For: 2.5.0
>
>
> Add a way to compute whether an execute-stage should be included, other than the simple service/component check.  
> For example some stage should only be executed if the cluster has Kerberos enabled.  This can be determined using the {{cluster-env/security_enabled}} flag; or (better yet) the {{Cluster}}'s {{securityType}} property, which would be set to "KERBEROS".
> Currently the only filter is based on service and component, which does not work in the case of Kerberos since Kerberos can be enabled without needing to install the KERBEROS service or the KERBEROS_CLIENT component. This will happen if the Kerberos identities are managed manually rather than configuring Ambari to do it by integrating with a supported KDC. 


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