We are heavily utilising back-sql on our product. Granted it has its issues but it does so far fulfill our needs. We are currently running on 2.4.58 which we build ourselves for Debian and RHEL/CentOS based systems. We needed couple of patches to back-sql to make it work for us. I just created issues (and added my patches) for them. I don't have a slightest idea if the patches are of any use for you but they make our environments work.
Removing back-sql from future releases would make us stuck with 2.4 release.
https://bugs.openldap.org/show_bug.cgi?id=9629 https://bugs.openldap.org/show_bug.cgi?id=9630
--- Aapo Romu --- Software Architect --- Eficode Oy
On Mon, 9 Aug 2021 at 00:02, Quanah Gibson-Mount quanah@symas.com wrote:
--On Sunday, August 8, 2021 6:32 PM +0100 Howard Chu hyc@symas.com wrote:
Quanah Gibson-Mount wrote:
For 2.5, we deprecated:
back-ndb back-sql back-perl
Should these be removed for 2.6?
I still routinely build back-perl in master. Is there any reason to remove it?
Not necessarily, that's why I started the discussion. back-bdb was deprecated with 2.3, but was around for all of 2.4 as well. I see no reason to keep back-ndb around. back-sql has numerous open issues, but I've no real insight into whether it retains any usefulness.
--Quanah
--
Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: http://www.symas.com
Aapo Romu wrote:
We are heavily utilising back-sql on our product. Granted it has its issues but it does so far fulfill our needs. We are currently running on 2.4.58 which we build ourselves for Debian and RHEL/CentOS based systems. We needed couple of patches to back-sql to make it work for us. I just created issues (and added my patches) for them. I don't have a slightest idea if the patches are of any use for you but they make our environments work.
Removing back-sql from future releases would make us stuck with 2.4 release.
back-sql has been without an official maintainer for quite a long time. Are you volunteering to keep it maintained from this point forward?
https://bugs.openldap.org/show_bug.cgi?id=9629 https://bugs.openldap.org/show_bug.cgi?id=9630
--- Aapo Romu --- Software Architect --- Eficode Oy
On Mon, 9 Aug 2021 at 00:02, Quanah Gibson-Mount <quanah@symas.com mailto:quanah@symas.com> wrote:
--On Sunday, August 8, 2021 6:32 PM +0100 Howard Chu <hyc@symas.com <mailto:hyc@symas.com>> wrote: > Quanah Gibson-Mount wrote: >> For 2.5, we deprecated: >> >> back-ndb >> back-sql >> back-perl >> >> Should these be removed for 2.6? > > I still routinely build back-perl in master. Is there any reason to > remove it? Not necessarily, that's why I started the discussion. back-bdb was deprecated with 2.3, but was around for all of 2.4 as well. I see no reason to keep back-ndb around. back-sql has numerous open issues, but I've no real insight into whether it retains any usefulness. --Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>
Hello, Howard and thank you for your offer of the maintainer role of back-sql. What kind of effort / how much work does maintaining an OpenLDAP backend module between releases usually take?
Eficode as a company is absolutely interested in supporting OpenLDAP development efforts and we started seeking for a better candidate for the back-sql maintainer role. We already may have a suitable candidate for you. I keep you posted about it once he has had some time to familiarise himself with the back-sql. Depending on the workload that comes from the maintenance of the back-sql I might be willing to temporarily look over things regarding that component if it would make it more probable to stay in the future releases of the OpenLDAP.
Best regards Aapo Romu
--- Aapo Romu --- Software Architect --- Eficode Oy
Aapo Romu wrote:
Hello, Howard and thank you for your offer of the maintainer role of back-sql. What kind of effort / how much work does maintaining an OpenLDAP backend module between releases usually take?
The intensity of effort is up to you. There are currently 26 tickets in the ITS for back-sql that have never been investigated. I have no idea how long any of them would take to address. It's up to you to see how much can be done between releases.
https://bugs.openldap.org/buglist.cgi?component=backends&f0=OP&f1=OP...
Eficode as a company is absolutely interested in supporting OpenLDAP development efforts and we started seeking for a better candidate for the back-sql maintainer role. We already may have a suitable candidate for you. I keep you posted about it once he has had some time to familiarise himself with the back-sql. Depending on the workload that comes from the maintenance of the back-sql I might be willing to temporarily look over things regarding that component if it would make it more probable to stay in the future releases of the OpenLDAP.
Best regards Aapo Romu
--- Aapo Romu --- Software Architect --- Eficode Oy
Hello, Howard
I'm sorry that it took so long to respond but we needed to figure out how we will arrange this.
So we are going to take a look at the back-sql tickets together with Eetu next Friday and start working from there. At some point (probably at the start of September) a third person will join us in the effort and I will gradually move away from the back-sql stuff.
Best regards Aapo Romu --- Aapo Romu --- Software Architect --- Eficode Oy
On Fri, 13 Aug 2021 at 17:14, Howard Chu hyc@symas.com wrote:
Aapo Romu wrote:
Hello, Howard and thank you for your offer of the maintainer role of
back-sql. What kind of effort / how much work does maintaining an OpenLDAP backend module between releases usually take?
The intensity of effort is up to you. There are currently 26 tickets in the ITS for back-sql that have never been investigated. I have no idea how long any of them would take to address. It's up to you to see how much can be done between releases.
https://bugs.openldap.org/buglist.cgi?component=backends&f0=OP&f1=OP...
Eficode as a company is absolutely interested in supporting OpenLDAP
development efforts and we started seeking for a better candidate for the back-sql maintainer role. We already may have a suitable candidate for you. I keep you posted about it once he has had some time to familiarise himself with the back-sql. Depending on the workload that comes from the maintenance of the back-sql I might be willing to temporarily look over things regarding that component if it would make it more probable to stay in the future releases of the OpenLDAP.
Best regards Aapo Romu
--- Aapo Romu --- Software Architect --- Eficode Oy
-- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/
--On Tuesday, August 17, 2021 5:07 PM +0300 Aapo Romu aapo.romu@eficode.com wrote:
Hello, Howard
I'm sorry that it took so long to respond but we needed to figure out how we will arrange this.
So we are going to take a look at the back-sql tickets together with Eetu next Friday and start working from there. At some point (probably at the start of September) a third person will join us in the effort and I will gradually move away from the back-sql stuff.
Best regards Aapo Romu
Hi Aapo,
Do you have any update on this? Unless someone actively steps up to maintain the back-sql backend we're leaning towards removing it, most likely in 2.7. The reported issues with it continue to expand and no one else has expressed any interest in maintaining it.
Regards, Quanah
-
Aapo Romu -
Howard Chu -
Quanah Gibson-Mount