ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Levas (JIRA)" <j...@apache.org>
Subject [jira] [Created] (AMBARI-16437) Add conditional constraints for Kerberos identities to control when they are created
Date Tue, 10 May 2016 18:43:12 GMT
Robert Levas created AMBARI-16437:
-------------------------------------

             Summary: Add conditional constraints for Kerberos identities to control when
they are created
                 Key: AMBARI-16437
                 URL: https://issues.apache.org/jira/browse/AMBARI-16437
             Project: Ambari
          Issue Type: Task
          Components: ambari-server
    Affects Versions: 2.4.0
            Reporter: Robert Levas
            Assignee: Robert Levas
             Fix For: 2.4.0


Add conditional constraints for Kerberos identities to control when they are created. For
example if Kerberos Identity should only be created (and distributed) for a component when
some other component or service is installed. 

An example of this would be
{code}
{
  "name": "/HIVE/HIVE_SERVER/hive_server_hive",
  "principal": {
    "configuration": "hive-interactive-site/hive.llap.daemon.service.principal"
  },
  "keytab": {
    "configuration": "hive-interactive-site/hive.llap.daemon.keytab.file"
  },
  "when" : {
      "contains" : ["services", "HIVE"]
  }
}
{code}

Note the "{{when}}" clause. This indicates that this identity should only be processed when
the set of services contains "HIVE".  An alternative to this would be to test the set of components
for a certain component. 




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

Mime
View raw message