Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Exclude Backends From Plugin Operations #1872

Open
389-ds-bot opened this issue Sep 13, 2020 · 6 comments
Open

Exclude Backends From Plugin Operations #1872

389-ds-bot opened this issue Sep 13, 2020 · 6 comments
Labels
priority_medium good value but complex/risky/not crucial
Milestone

Comments

@389-ds-bot
Copy link

Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/48812


Implement the suggestion in: http://www.port389.org/docs/389ds/design/exclude-backends-from-plugin-operations.html

@389-ds-bot 389-ds-bot added this to the 1.4 backlog milestone Sep 13, 2020
@389-ds-bot
Copy link
Author

Comment from nhosoi (@nhosoi) at 2016-05-05 23:42:29

Per triage, setting the milestone to 1.3.6.

Ludwig, please feel free to change it if you think differently. Thanks!

@389-ds-bot
Copy link
Author

Comment from tbordaz (@tbordaz) at 2016-06-16 18:39:00

Regarding provisioning performance use case (in freeipa deployement), this fix does not provide significant improvements (see http://www.freeipa.org/page/V4/Performance_Improvements#RetroCL_plugin).

@389-ds-bot
Copy link
Author

Comment from lkrispen (@elkris) at 2016-06-16 18:52:29

Replying to [comment:3 tbordaz]:

Regarding provisioning performance use case (in freeipa deployement), this fix does not provide significant improvements (see http://www.freeipa.org/page/V4/Performance_Improvements#RetroCL_plugin).

but you disabled memberof and slapi-nis, so the costly plugins are not called at all - the target of the fix was not a specific provisioning, but the normal run of a server, and not only performance, but also to avoid deadlocks

@389-ds-bot
Copy link
Author

Comment from lkrispen (@elkris) at 2017-02-11 23:11:42

Metadata Update from @elkris:

  • Issue assigned to elkris
  • Issue set to the milestone: 1.3.6 backlog

@389-ds-bot
Copy link
Author

Comment from mreynolds (@mreynolds389) at 2017-05-24 17:00:20

Metadata Update from @mreynolds389:

  • Issue close_status updated to: None
  • Issue set to the milestone: 1.3.7 backlog (was: 1.3.6 backlog)

@389-ds-bot
Copy link
Author

Comment from mreynolds (@mreynolds389) at 2019-08-23 21:13:39

Metadata Update from @mreynolds389:

  • Custom field reviewstatus adjusted to None
  • Issue set to the milestone: 1.4 backlog (was: 1.3.7 backlog)

@tbordaz tbordaz added the priority_medium good value but complex/risky/not crucial label Sep 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority_medium good value but complex/risky/not crucial
Projects
None yet
Development

No branches or pull requests

2 participants