Re: [Openstack-operators] [Openstack-Operators] Keystone cache strategies

2016-06-23 Thread Jose Castro Leon
f Matt Fischer Sent: Wednesday, June 22, 2016 5:07 AM To: Sam Morrison Cc: Jose Castro Leon ; openstack-operators@lists.openstack.org Subject: Re: [Openstack-operators] [Openstack-Operators] Keystone cache strategies On Tue, Jun 21, 2016 at 7:04 PM, Sam Morrison mailto:sorri...@gmail.com>> w

Re: [Openstack-operators] [Openstack-Operators] Keystone cache strategies

2016-06-21 Thread Matt Fischer
On Tue, Jun 21, 2016 at 7:04 PM, Sam Morrison wrote: > > On 22 Jun 2016, at 10:58 AM, Matt Fischer wrote: > > Have you setup token caching at the service level? Meaning a Memcache > cluster that glance, Nova etc would talk to directly? That will really cut > down the traffic. > > Yeah we have th

Re: [Openstack-operators] [Openstack-Operators] Keystone cache strategies

2016-06-21 Thread Sam Morrison
> On 22 Jun 2016, at 10:58 AM, Matt Fischer wrote: > > Have you setup token caching at the service level? Meaning a Memcache cluster > that glance, Nova etc would talk to directly? That will really cut down the > traffic. > Yeah we have that although the default cache time is 10 seconds for r

Re: [Openstack-operators] [Openstack-Operators] Keystone cache strategies

2016-06-21 Thread Matt Fischer
Have you setup token caching at the service level? Meaning a Memcache cluster that glance, Nova etc would talk to directly? That will really cut down the traffic. On Jun 21, 2016 5:55 PM, "Sam Morrison" wrote: > > On 22 Jun 2016, at 9:42 AM, Matt Fischer wrote: > > On Tue, Jun 21, 2016 at 4:21 P

Re: [Openstack-operators] [Openstack-Operators] Keystone cache strategies

2016-06-21 Thread Steve Martinelli
FWIW, we have refactored the revocation tree into a list, this should speed up the revocation process time significantly ( https://review.openstack.org/#/c/311652/) There is no way to disable revocations, since that would open up a security hole. On Tue, Jun 21, 2016 at 8:55 PM, Sam Morrison wro

Re: [Openstack-operators] [Openstack-Operators] Keystone cache strategies

2016-06-21 Thread Sam Morrison
> On 22 Jun 2016, at 9:42 AM, Matt Fischer wrote: > > On Tue, Jun 21, 2016 at 4:21 PM, Sam Morrison > wrote: >> >> On 22 Jun 2016, at 1:45 AM, Matt Fischer > > wrote: >> >> I don't have a solution for you, but I will concur that adding r

Re: [Openstack-operators] [Openstack-Operators] Keystone cache strategies

2016-06-21 Thread Matt Fischer
On Tue, Jun 21, 2016 at 4:21 PM, Sam Morrison wrote: > > On 22 Jun 2016, at 1:45 AM, Matt Fischer wrote: > > I don't have a solution for you, but I will concur that adding revocations > kills performance especially as that tree grows. I'm curious what you guys > are doing revocations on, anythin

Re: [Openstack-operators] [Openstack-Operators] Keystone cache strategies

2016-06-21 Thread Sam Morrison
> > On 22 Jun 2016, at 1:45 AM, Matt Fischer wrote: > > I don't have a solution for you, but I will concur that adding revocations > kills performance especially as that tree grows. I'm curious what you guys > are doing revocations on, anything other than logging out of Horizon? > Is there a

Re: [Openstack-operators] [Openstack-Operators] Keystone cache strategies

2016-06-21 Thread Matt Fischer
I don't have a solution for you, but I will concur that adding revocations kills performance especially as that tree grows. I'm curious what you guys are doing revocations on, anything other than logging out of Horizon? On Tue, Jun 21, 2016 at 5:45 AM, Jose Castro Leon wrote: > Hi all, > > While