As mentioned in the title, I found that placement does use cache token when accessing keystone api,resulting in slow response of the keystone interfaces.In fact, I found the keystone_authtoken config of placement was not transferred to keystone_middleware.
I tried to change one line of code in placement/wsgi.py +124 to “config = cig.CONF”,which effectively passed the configuration to keystone_middleware and used memcache.
Please help to confirm if it is a bug,thanks.
As mentioned in the title, I found that placement does use cache token when accessing keystone api,resulting in slow response of the keystone interfaces.In fact, I found the keystone_authtoken config of placement was not transferred to keystone_ middleware.
I tried to change one line of code in placement/wsgi.py +124 to “config = cig.CONF”,which effectively passed the configuration to keystone_middleware and used memcache.
Please help to confirm if it is a bug,thanks.