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

Fox, Kevin M Kevin.Fox at pnnl.gov
Fri Dec 4 00:37:30 UTC 2015


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 [ayoung at redhat.com]
Sent: Wednesday, December 02, 2015 8:00 PM
To: openstack-dev at lists.openstack.org
Subject: 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 the config. otherwise, the config as shipped with RDO worked fine. I am running giant radosgw, so future versions may not require that.

Thanks for the note.  Should this be bug?

>
> Thanks,
> Kevin
> ________________________________________
> From: Sean Dague [sean at dague.net]
> Sent: Tuesday, December 01, 2015 4:05 AM
> To: openstack-dev at lists.openstack.org
> Subject: 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 understanding is
> that Apache is specifically needed for Federation. Federation is the
> norm that we want for environments in the future.
>
> I'd hate to go down a path where the reference architecture we put out
> there doesn't support this. It's going to be all the pain of cells /
> non-cells that Nova's or nova-net / neutron bifurcation.
>
> Whatever the reference architecture is, it should support Federation. A
> non federation capable keystone should be the exception.
>
>> - uWSGI could help to support multiple web servers.
>
> --
> Sean Dague
> http://dague.net
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



More information about the OpenStack-dev mailing list