Wrong Mistral configuration

[Eduardo Gonzalez]

Mistral services are not working due to some misconfigurations.

The issues that currently exist in Mistral are:

- Non HAproxy configuration, Mistral endpoint points to HAproxy VIP, which will never reach a request to the service.

- API binds to 0.0.0.0, this is a security issue, also when using HAproxy in the same node, mistral_api containers will not start due "Address already in use".

- When bootstraping, after database upgrade, need to success a population, so action/workflows are present in the database. [0]

- Endpoints need Mistral version in the URL /v2

[0] http://docs.openstack.org/developer/mistral/guides/installation_guide.html#before-the-first-run

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/374921

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/374921
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=a71874f24f6da1361a1ccb7958780816e0dbc830
Submitter: Jenkins
Branch: master

commit a71874f24f6da1361a1ccb7958780816e0dbc830
Author: Eduardo Gonzalez <email address hidden>
Date: Thu Sep 22 17:27:14 2016 +0200

    Fix mistral service

    - Add mistral in HAproxy
    - Set mistral api to bind on api_interface
    - Fix mistral endpoint
    - Add database population on bootstraping
    - Add mistral port prechecks

    Change-Id: If1617fb9dcd8b3bbd4f94c68ca87c36e39711016
    Closes-Bug: #1626570

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/kolla 3.0.0.0rc2 release candidate.