[octavia-api][queens] broken pipe

Ignazio Cassano ignaziocassano at gmail.com
Wed Apr 3 08:17:36 UTC 2019

I solved using ocatvia-api under apache ,
I created a file under /etc/httpd/conf.d .
The file in octavia-api.conf:

Listen controlleraddress:9876

<VirtualHost *:9876>

    WSGIDaemonProcess octavia-wsgi user=octavia group=octavia processes=5
threads=1 display-name=%{GROUP}
    WSGIProcessGroup octavia-wsgi
    WSGIScriptAlias / /usr/local/bin/octavia-wsgi
    WSGIApplicationGroup %{GLOBAL}

    ErrorLog /var/log/httpd/octavia-wsgi.log

    <Directory /usr/local/bin/>
        WSGIProcessGroup octavia-wsgi
        <IfVersion >= 2.4>
            Require all granted
        <IfVersion < 2.4>
            Order allow,deny
            Allow from all

Il giorno mar 2 apr 2019 alle ore 16:39 Jeremy Stanley <fungi at yuggoth.org>
ha scritto:

> On 2019-04-02 14:57:56 +0200 (+0200), Ignazio Cassano wrote:
> > Do you know in which openstack version that fix wil be available ?
> [...]
> (Sorry for not including much context, the top-posting in your reply
> has made it extremely difficult to do so.) The "fix" mentioned by
> Brent, as I understand, is to simply use Apache with its mod_wsgi
> module to serve the API rather than exposing a WSGI service directly
> on a socket. If the deployment tooling you're using supports this
> operational model then you should simply be able to switch to it at
> any time. If your deployment tooling does not yet support this, then
> when it appears as an option in a release will depend on the tool in
> question. Are you asking when TripleO will switch to that model
> because you're using TripleO to manage your OpenStack deployment, or
> did you misunderstand the answer?
> --
> Jeremy Stanley
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20190403/ea4e3a6e/attachment.html>

More information about the openstack-discuss mailing list