[Openstack] [Keystone] Keystone Middleware Deprecate in-process token cache

Morgan Fainberg morgan.fainberg at gmail.com
Tue Apr 19 21:03:24 UTC 2016


On Tue, Apr 19, 2016 at 1:25 PM, Adam Young <ayoung at redhat.com> wrote:

> On 04/19/2016 01:55 AM, Kuo Hugo wrote:
>
> Hi Keystone Team,
>
> We aware this deprecation information in keystone middleware. I got couple
> of questions.
>
>
> https://github.com/openstack/keystonemiddleware/blob/6e58f8620ae60eb4f26984258d15a9823345c310/releasenotes/notes/deprecate-caching-tokens-in-process-a412b0f1dea84cb9.yaml
>
> We may need to update the document for Swift.
>
> I want to clarify that if Keystone team plan to deprecate support for the
> EnvCache (!?) or just the in-memory non-memcache option if you don't set
> *neither* memcached_servers *nor* env_cache .
>
> Thanks // Hugo
>
>
> _______________________________________________
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to     : openstack at lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>
> Doing proper tagging on subject.
>
> just in-memory is deprecated.  Memcache is sticking around.
>
> _______________________________________________
> Mailing list:
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to     : openstack at lists.openstack.org
> Unsubscribe :
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>
>
The in-process cache will be going away, but caching is sticking around as
would the ENVCache support (provided we can make it jive with oslo.cache).

We want to move to oslo.cache and not have default caching per-process that
results in inconsistent results depending on the process you hit for a
given endpoint (shared caches only).

--Morgan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20160419/fc265f38/attachment.html>


More information about the Openstack mailing list