Hello, thanks for tour answer.

I am not using tripleo but I installed openstack manually in high availability using haproxy.

I understood fine the issue is caused by haproxy when it tries to check Octavia api controllers and octavia api in not under apache.

Will tripleo modify haproxy rules or it will out octavia api under apache?

In the second case, is there any document for moving octavia api under apache in Centos 7 environments ?

Regards

ignazio

Il Mar 2 Apr 2019 16:39 Jeremy Stanley <fungi@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