You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Sebb (JIRA)" <ji...@apache.org> on 2016/04/11 11:12:25 UTC

[jira] [Created] (INFRA-11639) No fallback because ldap1-us-west and ldap2-us-west are now the same

Sebb created INFRA-11639:
----------------------------

             Summary: No fallback because ldap1-us-west and ldap2-us-west are now the same
                 Key: INFRA-11639
                 URL: https://issues.apache.org/jira/browse/INFRA-11639
             Project: Infrastructure
          Issue Type: Task
          Components: LDAP, Puppet
            Reporter: Sebb
            Priority: Minor


AFAICT, ldap1-us-west and ldap2-us-west are now the same as themis.

So there's no point including both in the same AuthLDAPUrl or ldapclient::ldapservers: entry.

This currently affects:

AuthLDAPUrl:
data/nodes/git1-us-west.apache.org.yaml
data/nodes/oauth-vm.apache.org.yaml
data/nodes/proxy1-us-west.apache.org.yaml
data/nodes/proxy2-us-west.apache.org.yaml
data/nodes/proxy3-us-west.apache.org.yaml

The above only use ldap1 and ldap2, so there is no fallback.

ldapclient::ldapservers:
data/colo/amz-vpc-virginia-1b.yaml
The above only uses ldap1 and ldap2:

These also use other servers (ldap3-us or ldap-lb-us):
data/colo/amz-vpc-us-west.yaml
data/colo/lw-us.yaml
data/colo/osuosl.yaml
data/colo/rax-vpc-us-mid.yaml
data/colo/vagrant.yaml
data/colo/yahoo.yaml





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