Increase exchange-api starting timeout value

[sirotsinskuy]

It would be good to have the exchange-api starting timeout bigger that 20 seconds (at least 30 sec, maybe up to 1 minute), as it could be the problem for some users. For my case - I was able to fit into that timeout after 3 times of trying and each time I had
Error: can not reach the exchange at http://127.0.0.1:3090/v1 (tried for 20 seconds): curl: (52) Empty reply from server

[joewxboy]

@bmpotter This is the second or third time I've heard this complaint from someone running the all-in-1 install script. On some machines and/or in some environments, they really need more time for the process to complete successfully. Would the solution be to increase the default timeout, allow an override for the timeout and discuss in documentation, or some other approach?

[bmpotter]

@joewxboy there already are overrides. See all of the env vars, starting at

devops/mgmt-hub/deploy-mgmt-hub.sh

Line 85 in 3b1e3f7

export HZN_LISTEN_IP=${HZN_LISTEN_IP:-127.0.0.1} # the host IP address the hub services should listen on. Can be set to 0.0.0.0 to mean all interfaces, including the public IP, altho this is not recommended, since the services use http.

. When there is syntax like:

export EXCHANGE_WAIT_ITERATIONS=${EXCHANGE_WAIT_ITERATIONS:-10}

that means use the value of EXCHANGE_WAIT_ITERATIONS the user has set in their environment, otherwise default to 10.

But i also just submitted a PR to increase the default and made you a reveiwer: #19