Re: [Openstack] Fwd: Call to API very slow [Grizzly]

2013-07-26 Thread Dan Reif
If for whatever reason you don't want to use the memcache token driver, I've seen an order-of-magnitude increase in performance simply from adding an index to the "expires" column in the token table. I opened a blueprint ( https://blueprints.launchpad.net/keystone/+spec/index-token-expiry) to get

Re: [Openstack] Deferred delete(soft delete) reclaim interval

2013-07-26 Thread Tiantian Gao
+1 Good point! Brian, The API looks great! Hoping more stackers agree with it. 2013/7/26 Brian Lamar > Hello! I have some comments below, but you might also consider posting > this question to > openstack-dev@lists.openstack.**orgas I'd > be curious as to the developer opinion on this questi

Re: [Openstack] Fwd: Call to API very slow [Grizzly]

2013-07-26 Thread Jay Pipes
On 07/25/2013 11:23 PM, Chu Duc Minh wrote: On Thu, Jul 25, 2013 at 7:30 PM, Jay Pipes mailto:jaypi...@gmail.com>> wrote: You will need to provide more details than "old" vs. "new" OpenStack. For example... 1) What is your network model in the old vs. new Old: nova-network + FlatD

Re: [Openstack] Deferred delete(soft delete) reclaim interval

2013-07-26 Thread Brian Lamar
Hello! I have some comments below, but you might also consider posting this question to openstack-...@lists.openstack.org as I'd be curious as to the developer opinion on this question. This list is mostly for users/operators of OpenStack clouds. Tiantian Gao wrote: Hi stackers, Now when re

[Openstack] Deferred delete(soft delete) reclaim interval

2013-07-26 Thread Tiantian Gao
Hi stackers, Now when reclaim_instance_interval is great than 0, the delete action will become soft_delete. How about let user to specify the reclaim_instance_interval? does that make sense? or anybody have the same requirement? Because currently implemented the reclaim_instance_interval is syst