RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 663893 - [RFE] Dispaching LDAP requested with weight/or in round robin fashion
Summary: [RFE] Dispaching LDAP requested with weight/or in round robin fashion
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: sssd
Version: 6.0
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: rc
: ---
Assignee: Stephen Gallagher
QA Contact: Chandrasekar Kannan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-12-17 08:46 UTC by Frederic Hornain
Modified: 2015-01-04 23:45 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-12-17 11:28:14 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Frederic Hornain 2010-12-17 08:46:09 UTC 
Description of problem:

Could it be possible in the next releases to specify several Directory Servers associated to weight or a round robin option.
Like this the LDAP Client is not going to always ask to the same Directory Server all its requests even if several LDAP are defined.

If it is not clear, feel free to contact me for more details.

BR
Frederic ;)
Comment 2 Stephen Gallagher 2010-12-17 11:28:14 UTC 
SERVICE DISCOVERY
       The service discovery feature allows back ends to automatically find
       the appropriate servers to connect to using a special DNS query.

   Configuration
       If no servers are specified, the back end automatically uses service
       discovery to try to find a server. Optionally, the user may choose to
       use both fixed server addresses and service discovery by inserting a
       special keyword, “_srv_”, in the list of servers. The order of
       preference is maintained. This feature is useful if, for example, the
       user prefers to use service discovery whenever possible, and fall back
       to a specific server when no servers can be discovered using DNS.

   The domain name
       Please refer to the “dns_discovery_domain” parameter in the
       sssd.conf(5) manual page for more defails.


       dns_discovery_domain (string)
           If service discovery is used in the back end, specifies the domain part of the service discovery DNS query.

           Default: Use the domain part of machine´s hostname

   The protocol
       The queries usually specify _tcp as the protocol. Exceptions are
       documented in respective option description.

   See Also
       For more information on the service discovery mechanism, refer to RFC
       2782.



When using DNS discovery, RFC 2782 specifies a weighted round-robin approach. So to accomplish what you're asking for, it can already be done simply by setting SSSD to use DNS SRV records as described above, and configuring the SRV records on your DNS server according to RFC 2782.
Comment 3 Frederic Hornain 2010-12-17 14:05:25 UTC 
Well, you are perfectly right. 
I did not think about that. 
Well done !

BR
Frederic ;)
Note You need to log in before you can comment on or make changes to this bug.