Open Stack

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 it.
>
> So, in short, officially keystone does not support chunked encoding. 
> If radosgw cannot work without it, it is a bug against radosgw or 
> something RDO itself is doing with radosgw.
>

RDO is not doing Keystone in HTTPD by default yet, and I have not come 
across the radosgw module at all.  Didn't think it was a real issue, but 
want to track if it is.

> --morgan
>
> On Dec 2, 2015 23:00, "Adam Young" <ayoung at redhat.com 
> <mailto:ayoung at redhat.com>> wrote:
>
>     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 <mailto:sean at dague.net>]
>         Sent: Tuesday, December 01, 2015 4:05 AM
>         To: openstack-dev at lists.openstack.org
>         <mailto: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://OpenStack-dev-request@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://OpenStack-dev-request@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://OpenStack-dev-request@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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20151203/9d64f8a5/attachment.html>