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

Benchmarks always appreciated! But, these types of benchmarks are *entirely* useless unless you can provide the exact configuration you used for each scenario so that others can scrutinize the test method and reproduce your results. So, off the top of my head, I'm looking for: * keystone.conf *

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

Sounds good Dolph. Will try to post the details as requested on gist/ blog shortly. Regards, Ali From: Dolph Mathews > Reply-To: "OpenStack Development Mailing List (not for usage questions)"

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

On 12/08/2015 06:39 AM, Jamie Lennox wrote: > The main problem I see with running Keystone (or any other service) in a > web server, is that *I* (as a package maintainer) will loose the control > over when the service is started. Let me explain why that is important > for me. > >

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

So in any case i am using 20 processes and 20 threads to have optimal utilization. I did try with 50 50 values too for apache and the utilization spikes a bit high but its fine for load test. Utilization do touch around 40% for 20 20 values of processes and threads.I am running it on BM with 128gb

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

Hi Dolph/team: As requested I have outlined most of the files and configs to give more clear picture @ https://gist.github.com/noah8713/7d5554d78b60cd9a4999: * keystone.conf —uploaded * distro used for testing, in case they override the project's defaults —mentioned * all nginx config files

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

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

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

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

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

On Tue, Dec 1, 2015 at 12:57 AM, Steve Martinelli wrote: > Trying to summarize here... > > - There isn't much interest in keeping eventlet around. > - Folks are OK with running keystone in a WSGI server, but feel they are > constrained by Apache. > - uWSGI could help to

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

On Dec 7, 2015 17:51, "Brant Knudson" wrote: > > > > On Tue, Dec 1, 2015 at 12:57 AM, Steve Martinelli wrote: >> >> Trying to summarize here... >> >> - There isn't much interest in keeping eventlet around. >> - Folks are OK with running keystone in a WSGI

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

... re-adding the operators mailing list. sounds like we should document how to do this, with the assertion that it is not tested with our CI. with that said, we should try to have a job that sets up keystone with nginx that is run periodically (similar to our eventlet job at the moment).

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

On Mon, Dec 07, 2015 at 06:18:04PM -0500, Steve Martinelli wrote: > > ... re-adding the operators mailing list. > > sounds like we should document how to do this, with the assertion that it > is not tested with our CI. > > with that said, we should try to have a job that sets up keystone with >

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

On 12/01/2015 07:57 AM, Steve Martinelli wrote: > Trying to summarize here... > > - There isn't much interest in keeping eventlet around. > - Folks are OK with running keystone in a WSGI server, but feel they are > constrained by Apache. > - uWSGI could help to support multiple web servers. > >

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

On 8 December 2015 at 07:53, Thomas Goirand wrote: > On 12/01/2015 07:57 AM, Steve Martinelli wrote: > > Trying to summarize here... > > > > - There isn't much interest in keeping eventlet around. > > - Folks are OK with running keystone in a WSGI server, but feel they are > >

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

Chunked Encoding is a bad idea with mod_wsgi in general. While enabling it like that is fine, you are not guaranteed to get 100% consistent results simply because the wsgi spec did not/does not support it. Not all versions of mod_wsgi can enable it. So, in short, officially keystone does not

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

On 12/03/2015 07:51 AM, Morgan Fainberg wrote: Chunked Encoding is a bad idea with mod_wsgi in general. While enabling it like that is fine, you are not guaranteed to get 100% consistent results simply because the wsgi spec did not/does not support it. Not all versions of mod_wsgi can enable

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

Not really sure. If its reproducible with hammer+, I'd say yes. giant's keystone support was very basic, and it may not work against Mitaka anyway? It only supports v2. Thanks, Kevin From: Adam Young [ayo...@redhat.com] Sent: Wednesday, December 02, 2015

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

On 12/01/2015 03:50 PM, Fox, Kevin M wrote: I just upgraded to keystone liberty for one of my production clouds, and went with apache since eventlet was listed as deprecated. It was pretty easy. Just ran into one issue. RadosGW wouldn't work against it until I added "WSGIChunkedRequest On'" in

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

On Tue, Dec 1, 2015 at 1:57 AM, Steve Martinelli wrote: > Trying to summarize here... > > - There isn't much interest in keeping eventlet around. > - Folks are OK with running keystone in a WSGI server, but feel they are > constrained by Apache. > - uWSGI could help to

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

I just upgraded to keystone liberty for one of my production clouds, and went with apache since eventlet was listed as deprecated. It was pretty easy. Just ran into one issue. RadosGW wouldn't work against it until I added "WSGIChunkedRequest On'" in the config. otherwise, the config as shipped

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

On Tuesday 01 December 2015 08:50:14 Lance Bragstad wrote: > On Tue, Dec 1, 2015 at 6:05 AM, Sean Dague wrote: > > > > From an interop perspective, this concerns me a bit. My > > understanding is that Apache is specifically needed for > > Federation. Federation is the norm that

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

On 12/01/2015 01:57 AM, Steve Martinelli wrote: > Trying to summarize here... > > - There isn't much interest in keeping eventlet around. > - Folks are OK with running keystone in a WSGI server, but feel they are > constrained by Apache. >From an interop perspective, this concerns me a bit. My

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

On Tue, Dec 1, 2015 at 6:05 AM, Sean Dague wrote: > On 12/01/2015 01:57 AM, Steve Martinelli wrote: > > Trying to summarize here... > > > > - There isn't much interest in keeping eventlet around. > > - Folks are OK with running keystone in a WSGI server, but feel they are > >

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

Trying to summarize here... - There isn't much interest in keeping eventlet around. - Folks are OK with running keystone in a WSGI server, but feel they are constrained by Apache. - uWSGI could help to support multiple web servers. My opinion: - Adding support for uWSGI definitely