Set notification_bind on zaqar websocket

Don't let zaqar websocket listen to notifications on all interfaces:
otherwise, it uses the hostname as a subscription target, and it doesn't
work when the host is set as an IPv6 host. Ultimately this should be
fixed in Zaqar, but this will work around it for now.

Change-Id: Ib7ece313371660ea02bef314bf5b5d2c4121a884
Related-Bug: #1727406
This commit is contained in:
Dan Prince 2017-11-01 08:49:01 -04:00
parent d6a2160b82
commit 41a3194901
1 changed files with 1 additions and 0 deletions

View File

@ -106,6 +106,7 @@ outputs:
- {get_param: ZaqarDebug }
zaqar::server::service_name: 'httpd'
zaqar::transport::websocket::bind: {get_param: [EndpointMap, ZaqarInternal, host]}
zaqar::transport::websocket::notification_bind: {get_param: [EndpointMap, ZaqarInternal, host]}
zaqar::wsgi::apache::ssl: {get_param: EnableInternalTLS}
zaqar::wsgi::apache::bind_host: {get_param: [ServiceNetMap, ZaqarApiNetwork]}
zaqar::message_pipeline: 'zaqar.notification.notifier'