<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">On 12/03/2015 07:51 AM, Morgan Fainberg
      wrote:<br>
    </div>
    <blockquote
cite="mid:CAGnj6avp2=p_Xfk_s_wTVAZgL0gNENPFecaCfyc9U7+=6rbqxg@mail.gmail.com"
      type="cite">
      <p dir="ltr">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. </p>
      <p dir="ltr">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. </p>
    </blockquote>
    <br>
    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.<br>
    <br>
    <blockquote
cite="mid:CAGnj6avp2=p_Xfk_s_wTVAZgL0gNENPFecaCfyc9U7+=6rbqxg@mail.gmail.com"
      type="cite">
      <p dir="ltr">--morgan</p>
      <div class="gmail_quote">On Dec 2, 2015 23:00, "Adam Young" <<a
          moz-do-not-send="true" href="mailto:ayoung@redhat.com"><a class="moz-txt-link-abbreviated" href="mailto:ayoung@redhat.com">ayoung@redhat.com</a></a>>
        wrote:<br type="attribution">
        <blockquote class="gmail_quote" style="margin:0 0 0
          .8ex;border-left:1px #ccc solid;padding-left:1ex">On
          12/01/2015 03:50 PM, Fox, Kevin M wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            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.<br>
          </blockquote>
          <br>
          Thanks for the note.  Should this be bug?<br>
          <br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <br>
            Thanks,<br>
            Kevin<br>
            ________________________________________<br>
            From: Sean Dague [<a moz-do-not-send="true"
              href="mailto:sean@dague.net" target="_blank">sean@dague.net</a>]<br>
            Sent: Tuesday, December 01, 2015 4:05 AM<br>
            To: <a moz-do-not-send="true"
              href="mailto:openstack-dev@lists.openstack.org"
              target="_blank">openstack-dev@lists.openstack.org</a><br>
            Subject: Re: [openstack-dev] [Openstack-operators]
            [keystone] Removing functionality that was deprecated in
            Kilo and upcoming deprecated functionality in Mitaka<br>
            <br>
            On 12/01/2015 01:57 AM, Steve Martinelli wrote:<br>
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">
              Trying to summarize here...<br>
              <br>
              - There isn't much interest in keeping eventlet around.<br>
              - Folks are OK with running keystone in a WSGI server, but
              feel they are<br>
              constrained by Apache.<br>
            </blockquote>
             From an interop perspective, this concerns me a bit. My
            understanding is<br>
            that Apache is specifically needed for Federation.
            Federation is the<br>
            norm that we want for environments in the future.<br>
            <br>
            I'd hate to go down a path where the reference architecture
            we put out<br>
            there doesn't support this. It's going to be all the pain of
            cells /<br>
            non-cells that Nova's or nova-net / neutron bifurcation.<br>
            <br>
            Whatever the reference architecture is, it should support
            Federation. A<br>
            non federation capable keystone should be the exception.<br>
            <br>
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">
              - uWSGI could help to support multiple web servers.<br>
            </blockquote>
            <br>
            --<br>
            Sean Dague<br>
            <a moz-do-not-send="true" href="http://dague.net"
              rel="noreferrer" target="_blank">http://dague.net</a><br>
            <br>
__________________________________________________________________________<br>
            OpenStack Development Mailing List (not for usage questions)<br>
            Unsubscribe: <a moz-do-not-send="true"
href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe"
              rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
            <a moz-do-not-send="true"
              href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"
              rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
            <br>
__________________________________________________________________________<br>
            OpenStack Development Mailing List (not for usage questions)<br>
            Unsubscribe: <a moz-do-not-send="true"
href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe"
              rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
            <a moz-do-not-send="true"
              href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"
              rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
          </blockquote>
          <br>
          <br>
__________________________________________________________________________<br>
          OpenStack Development Mailing List (not for usage questions)<br>
          Unsubscribe: <a moz-do-not-send="true"
href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe"
            rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
          <a moz-do-not-send="true"
            href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"
            rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
        </blockquote>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: <a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>