ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Hurley (JIRA)" <j...@apache.org>
Subject [jira] [Created] (AMBARI-18726) Upgrade Orchestration Groups And Stages Should Be Conditionally Controlled
Date Fri, 28 Oct 2016 03:58:58 GMT
Jonathan Hurley created AMBARI-18726:
----------------------------------------

             Summary: Upgrade Orchestration Groups And Stages Should Be Conditionally Controlled
                 Key: AMBARI-18726
                 URL: https://issues.apache.org/jira/browse/AMBARI-18726
             Project: Ambari
          Issue Type: Task
          Components: ambari-server
    Affects Versions: 2.5.0
            Reporter: Jonathan Hurley
            Assignee: Jonathan Hurley
            Priority: Critical
             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)

Mime
View raw message