List role assignments filters performance
Bug #1359231 reported by
Samuel de Medeiros Queiroz
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Invalid
|
Wishlist
|
Samuel de Medeiros Queiroz |
Bug Description
When listing role assignments, we have the option to filter them by actor, target and role.
As Henry Nash pointed out at [1] , the current implementation uses the standard filtering the V3.wrap_collection. Given the large number of individual assignments, this is pretty inefficient.
The controller should pass the filters into the driver call, so that the list size is kept a minimum.
For example, if the user wants to filter role assignments by project X, the driver would query the DB only selecting the role assignments where target_id = X.id, instead of querying everything and returning the result to be filtered by the controller.
description: | updated |
Changed in keystone: | |
assignee: | nobody → Samuel de Medeiros Queiroz (samuel-z) |
tags: | added: performance |
Changed in keystone: | |
assignee: | Samuel de Medeiros Queiroz (samuel-z) → Rodrigo Duarte (rodrigodsousa) |
Changed in keystone: | |
assignee: | Rodrigo Duarte (rodrigodsousa) → Samuel de Medeiros Queiroz (samuel-z) |
Changed in keystone: | |
assignee: | Samuel de Medeiros Queiroz (samuel-z) → Rodrigo Duarte (rodrigodsousa) |
Changed in keystone: | |
assignee: | Rodrigo Duarte (rodrigodsousa) → Samuel de Medeiros Queiroz (samuel-z) |
To post a comment you must log in.
I agree that this should be fixed for the assignment SQL backend.