Browse Source

Add tunnel timeout for ui proxy container

Add an explicit tunnel timeout configuration option to increase the
tunnel timeout for persistent socket connections from two minutes (2m)
to one hour (3600s).  A configuration was already present to apply a
tunnel timeout to the zaqar_ws endpoint, but that only applies to
connections made directly to the zaqar_ws endpoint directly.  Since UI
now uses mod_proxy to proxy WebSocket connections for Zaqar, the timeout
is now applied for the same reasons to the ui haproxy server.

Change-Id: If749dc9148ccf8f2fa12b56b6ed6740f42e65aeb
Closes-Bug: 1672826
changes/17/452017/2
Dan Trainor 3 years ago
parent
commit
e8125cb364
2 changed files with 12 additions and 0 deletions
  1. +6
    -0
      manifests/haproxy.pp
  2. +6
    -0
      releasenotes/notes/add-tunnel-timeout-for-haproxy-ui-0705dfd671f9f487.yaml

+ 6
- 0
manifests/haproxy.pp View File

@ -1595,6 +1595,12 @@ class tripleo::haproxy (
server_names => $controller_hosts_names_real,
mode => 'http',
public_ssl_port => $ports[ui_ssl_port],
listen_options => {
# NOTE(dtrainor): in addition to the zaqar_ws endpoint, the HTTPS
# (443/tcp) endpoint that answers for the UI must also use a long-lived
# tunnel timeout for the same reasons mentioned above.
'timeout' => ['tunnel 3600s'],
},
}
}
if $contrail_config {


+ 6
- 0
releasenotes/notes/add-tunnel-timeout-for-haproxy-ui-0705dfd671f9f487.yaml View File

@ -0,0 +1,6 @@
---
fixes:
- |
Add a tunnel timeout to the HAProxy tripleo-ui configuration to ensure
Zaqar WebSocket tunnels persist longer than two minutes
https://bugs.launchpad.net/tripleo/+bug/1672826

Loading…
Cancel
Save