yahoo-eng-team team mailing list archive

[Morgan Fainberg <morgan.fainberg@xxxxxxxxx>]

As a concern for backwards compatibility, and because we rely on the
schema as a basis for allowable size (in this case 64) we cannot always
reduce this.

If someone has data out there that is using more than the 32bytes for
the id (custom driver, custom domain/project/etc) we would
truncate/break those users.

For user and group ids we (in some cases) use a sha256 hash (64 bytes)
of data to map the information to the multiple LDAP backends that are
now configurable. While this can make a minor improvement to the
performance of the DB this is a bit of over optimization and could cause
data loss in some active deployments.

** Changed in: keystone
       Status: New => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1361238

Title:
  Too huge space reserved for tenant_id/user_id/domain_id in the
  database

Status in OpenStack Identity (Keystone):
  Invalid

Bug description:
  Keystone uses 32 byte/character domain/user/project id , which
  contains a hexadecimal representation of 128 bit (16 byte) integer,
  but the database field is a varchar(64).

  Please reduce the filed size at least to 32 byte varchar, it helps to
  the db for using the caches (disk/ memory/ record per physical
  sector..) more efficiently.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1361238/+subscriptions