[Bug 1582585] Re: the speed of query user from ldap server is very slow

[Corey Bryant]

Thanks for the patches Billy. I've reviewed the patches and I think they
justify an SRU.

Some notes from my review:
* Patches 1 through 3 are fairly straight forward cherry-picks that are already in Newton and require a very minimal changes to apply to Mitaka.
* Patch 3 adds a new 'mapping_populate' subcommand to keystone-manage that enables creation of id mapping entries. This is a feature, and while we typically don't backport features, I think this case is warranted as it is an optional command that allows an admin to pre-create pubic IDs to prevent users from hitting costly CLI/API calls.
* Patch requires additional code to handle backends that don't support get_domain_mapping_list(). I want to make sure testing of the fallback path is performed in addition to the new path.

To avoid regression of existing consumers, the OpenStack team will run
their continuous integration tests against the packages that are in
-proposed.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1582585

Title:
  the speed of query user from ldap server is very slow

Status in Ubuntu Cloud Archive:
  New
Status in Ubuntu Cloud Archive mitaka series:
  Triaged
Status in Ubuntu Cloud Archive newton series:
  Triaged
Status in OpenStack Identity (keystone):
  Fix Released
Status in keystone package in Ubuntu:
  New
Status in keystone source package in Xenial:
  Triaged

Bug description:
  In our project, the speed of query user from ldap server is very
  slow,our ldap user number is 12,000,the query costs almost 45 seconds

  The reason is that keystone will generate the uuid for the ldap users one by one and insert db.And second query time later,it also goes to db,not use the cache.
  So adding the cache to improve the query speed

  After adding @MEMOIZE to the following function
  https://github.com/openstack/keystone/blob/master/keystone/identity/core.py#L580.
  First query time almost costs 50 seconds,but second query time later it only costs 7 seconds.

  So it is very necessary to improve this feature

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1582585/+subscriptions