I suggest we either choose the option 3) from https://bugs.launchpad.net/mos/+bug/1621541/comments/13 (as nova-api seems to be the only service for which we configure caching of token validation in keystonemiddleware.auth_token by the means of memcached http://paste.openstack.org/show/585192/) or, alternatively, only point keystonemiddleware.auth_token to the *local* memcached, if we *really* want to reuse the results of token validation between multiple nova-api processes (we usually run multiple forks).
MOS DA team, could you please take a look at this one? ^
I suggest we either choose the option 3) from https:/ /bugs.launchpad .net/mos/ +bug/1621541/ comments/ 13 (as nova-api seems to be the only service for which we configure caching of token validation in keystonemiddlew are.auth_ token by the means of memcached http:// paste.openstack .org/show/ 585192/) or, alternatively, only point keystonemiddlew are.auth_ token to the *local* memcached, if we *really* want to reuse the results of token validation between multiple nova-api processes (we usually run multiple forks).
MOS DA team, could you please take a look at this one? ^