Sumit Jamgade b4b625c9f5 start tls-proxy (if enabled) before checking for api ...

When tls-proxy is enabled, first start the tls-proxy and then then wait
for api to come up.

Without this the api comes up on the internal port as a result the
subsequent curl fails killing the deployment
- create a zuul job to test with tls
- fix apache ports accordingly

Depends-On: Ie665240b53df92b8e5ca509e998e95d859bd5282
Change-Id: I610a7a24daab68c7ab0e30977e3cabd62cdb56a5

2018-11-21 18:47:47 +01:00

..

files

Run Watcher-API behind mod-wsgi

2017-04-01 19:03:17 +05:30

lib

start tls-proxy (if enabled) before checking for api

2018-11-21 18:47:47 +01:00

local.conf.compute

[Doc] fix local.conf.compute

2017-04-24 20:58:37 +09:00

local.conf.controller

Remove explicitly enable neutron

2017-10-10 01:59:46 +00:00

plugin.sh

Fix to use . to source script files

2017-08-29 18:01:09 +08:00

settings

Fix tempest devstack error

2018-01-18 23:33:08 -08:00