Re: [openstack-dev] [Openstack-operators] [keystone] Removing functionality that was deprecated in Kilo and upcoming deprecated functionality in Mitaka

2015-12-09 Thread Ginwala, Aliasgar
Choosing between them should not be a matter of performance, but it should be a choice of documentation, licensing, community, operability, supportability, reliability, etc. Performance should be relatively similar, and thus a much lower priority in making your selection. On Tue, Dec 8, 2015 at 10:09 PM, Gi

Re: [openstack-dev] [Openstack-operators] [keystone] Removing functionality that was deprecated in Kilo and upcoming deprecated functionality in Mitaka

2015-12-09 Thread Ginwala, Aliasgar
er priority in making your selection. On Tue, Dec 8, 2015 at 10:09 PM, Ginwala, Aliasgar <aginw...@ebay.com<mailto:aginw...@ebay.com>> wrote: Hi All: Just to inform Steve and all the folks who brought up this talk ;We did some benchmarking using wsgi, apache and nginx for keysto

[openstack-dev] [Openstack-operators] [keystone] Removing functionality that was deprecated in Kilo and upcoming deprecated functionality in Mitaka

2015-12-08 Thread Ginwala, Aliasgar
Hi All: Just to inform Steve and all the folks who brought up this talk ;We did some benchmarking using wsgi, apache and nginx for keystone with mysql as token backend and we got following results on Juno version. Hence I am just giving you brief highlight about the results we got. spawning