Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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.

Description of problem:

It seems ldirectord is not/no longer shipped with the resource agents in RHEL7.

Ldirectord can easily be configured in combination with pacemaker. Keepalived provides a similar setup but does not need pacemaker. I failed to discover if/how keepalived can be combined with pacemaker so pacemaker handles the failover part.

For clusters that already run pacemaker for other services, ldirectord is much easier to setup and seems to provide better integration.

Please consider shipping ldirectord (as a tech preview if necessary) in a future update.

Regards,

Rik

(In reply to Rik Theys from comment #0)
> Description of problem:
> 
> It seems ldirectord is not/no longer shipped with the resource agents in
> RHEL7.

ldirectord was never supported in rhel7 resource-agents. We use HAProxy for load balancing. 

are there any technical advantages to ldirectord over HAProxy?

Hi,

HAproxy proxies the connections and uses an additional tcp session to the backend. It adds a small latency and all the responses from the backend servers have to go through the HAproxy. With HAproxy the real servers don't see the IP of the client (unless with some specific headers, which are not available for every protocol).

Ldirectord uses LVS and the responses from the backend servers go straight to the client (depending on the setup). There's no additional tcp connection to set up in the case of ldirectord. 



Regards,

Rik

Red Hat has evaluated the requested for inclusion of ldirectord in the distribution and decided not to support/ship it.

Alternative solutions, such as haproxy and keepalived already exists in the product in a supported fashion.