SSSD 2.0 and breaking compatibility
by Jakub Hrozek
Hi Timo, Howard and sssd-devel list,
Over time, there has been a lot of functionality, but also a bit of cruft accumulated in SSSD. We’ve been discussing removing some old code for some time with the other RH developers and we’d like to propose that the next .0 is the one that breaks the backwards compatibility a bit. We’d also like to signify that the release is important by bumping the major version number and calling the release 2.0.
We’ve been (provisionally) putting the tickets that break compatibility into the 2.0 milestone in Pagure and tagging them with “breaks compatibility” so you can find them here:
https://pagure.io/SSSD/sssd/roadmap?status=Open&tag=breaks+compatibility&...
I think most of what we propose to remove is fairly obscure and I even hope none of the features is actually used.
Apart from those, we’d also like to switch the default upstream crypto from Mozilla NSS to OpenSSL:
https://pagure.io/SSSD/sssd/issue/3495
There are other things we’d like to highlight with bumping the version to 2.0 like the ability to socket-activate services or using just drop-in config files with no sssd.conf at all, but the thing I think should be discussed first is the backwards (in)compatibility..
Because SSSD release schedule is often related to the Fedora release schedule, we’d like to propose that the release that breaks compatibility happens before the Beta deadline of the next Fedora release:
https://fedoraproject.org/wiki/Releases/28/Schedule
specifically:
2018-02-20 - Branch Fedora 28 from Rawhide (Rawhide becomes future F29)
This doesn’t have to be 2.0 per se but perhaps 2.0-beta, the important thing to us is to remove the code for F-28.
What I’m wondering is:
- Do you have any concerns with removing these features in general? Do you know if any of your users or customes rely on these features?
- Would this release schedule fit into your distributions’ schedule?
Thank you for your help!
5 years, 9 months
[sssd PR#453][opened] Speed up by-ID lookups with the help of the Global Catalog
by jhrozek
URL: https://github.com/SSSD/sssd/pull/453
Author: jhrozek
Title: #453: Speed up by-ID lookups with the help of the Global Catalog
Action: opened
PR body:
"""
These patches implement the RFE requested in
https://pagure.io/SSSD/sssd/issue/3468
The design page was sent to sssd-devel for review as:
https://lists.fedorahosted.org/archives/list/sssd-devel@lists.fedorahoste...
but so far was not merged.
Please see the design page for explanation of the general flow, but also
feel free to point out if more comments should be added to the code
so that developers don't have to go back to design pages.
There are still some things I'm working on, but I think at least the
cache_req part should be ready for review.
Here's what I think is not finished yet:
- I don't think the locate domain request works for MPG domains
- unit tests should be added for the negcache API additions as well
as the DP interface to not decrease the code coverage
- I still haven't made up my mind if we should support also the
object-by-ID request. I think it would be nice for completeness
but I also think it's not strictly required
- I only ran several downstream tests, not all, so I don't know
if there are some regressions or not
"""
To pull the PR as Git branch:
git remote add ghsssd https://github.com/SSSD/sssd
git fetch ghsssd pull/453/head:pr453
git checkout pr453
5 years, 9 months