#2188 automatically assign new slices for any AD domain
Closed: Fixed None Opened 7 years ago by simo.

When a domain RID grows beyond the slice size it may make sense to have sssd allocate a new slice automatically instead of relying on the admin to find the fault and increase the slice size.
this also helps if there are large gaps in the RID space so that smaller slices are used.

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.13 beta
rhbz: => todo

Fields changed

mark: => 0

Makes sense, but perhaps we won't have the time in 1.13.

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

I ran into two cases that hit the hardcoded range size this week. We might want to reconsider. The cheap way would be to log more prominently.

milestone: SSSD 1.14 beta => NEEDS_TRIAGE

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.13 backlog

Fields changed

priority: major => critical
sensitive: => 0

The IPA provider of SSSD always get the idranges from the server, see FreeIPA ticket.

For the AD provider we can add a scheme similar to the one used by the samba autorid module. If there is the RID outside of the rage detected calculate the integer part of RID/range_size and append this to the domain name as domain_name#N. Then take the hash value of domain_name#N to find a new slices for the RID.

Fields changed

owner: somebody => preichl

This ticket shouldn't be in the backlog but 1.13.4

milestone: SSSD 1.13 backlog => SSSD 1.13.4

Fields changed

patch: 0 => 1



resolution: => fixed
status: new => closed

Metadata Update from @simo:
- Issue assigned to preichl
- Issue set to the milestone: SSSD 1.13.4

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/3230

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.