#2394 redesign failover
Closed: wontfix 4 years ago by pbrezina. Opened 9 years ago by pbrezina.

Our AD integration has outgrown current failover code. The failover was not designed to support subdomains and we are running in more and more problems which are harder to fix.

The main problem is that the current failover has one context for the whole sssd_be process which makes it impossible to have different settings for root domain and its subdomains. We should redesign the failover in a way that there will be one separate context per domain.

We may also want to implement additional features like caching mechanism (since global catalog servers are the same for all AD forest).


Fields changed

blockedby: => #2393 #1083

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.13 beta

Fields changed

rhbz: => 0

Fields changed

mark: => 0

Fields changed

milestone: SSSD 1.13 beta => SSSD 1.13 backlog

Mass-moving tickets not planned for the 1.13 release to 1.14

milestone: SSSD 1.13 backlog => SSSD 1.14 beta

This would be nice to have, but the changes required for the failover and responder refactoring are not scoped for the 1.14 release.

milestone: SSSD 1.14 beta => SSSD 1.15 beta
sensitive: => 0

Metadata Update from @pbrezina:
- Issue marked as depending on: #1083
- Issue marked as depending on: #2393
- Issue set to the milestone: SSSD Future releases (no date set yet)

7 years ago

Metadata Update from @thalman:
- Custom field blocking adjusted to 1083,2393
- Custom field design_review reset (from 0)
- Custom field mark reset (from 0)
- Custom field patch reset (from 0)
- Custom field review reset (from 0)
- Custom field sensitive reset (from 0)
- Custom field testsupdated reset (from 0)
- Issue close_status updated to: None
- Issue tagged with: Canditate to close

4 years ago

Thank you for taking time to submit this request for SSSD. Unfortunately this issue was not given priority and the team lacks the capacity to work on it at this time.

Given that we are unable to fulfill this request I am closing the issue as wontfix.

If the issue still persist on recent SSSD you can request re-consideration of this decision by reopening this issue. Please provide additional technical details about its importance to you.

Thank you for understanding.

Metadata Update from @pbrezina:
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)

4 years ago

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/3436

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Login to comment on this ticket.

Metadata