[NETCONF-475] Unable to specify IP address for websocket to bind to Created: 05/Oct/17 Updated: 15/Mar/19 Resolved: 13/Oct/17 |
|
| Status: | Verified |
| Project: | netconf |
| Component/s: | restconf-nb |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Tim Rozet | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 9256 |
| Description |
|
By default the websocket server will listen on 0.0.0.0 which is not acceptable in a clustered environment where we are using haproxy to bind a virtual IP for ODL and load balance websocket connections. It is also unsafe to bind to 0.0.0.0. There is currently no way to specify the IP address to bind to, only config available is to change the port. |
| Comments |
| Comment by Tomas Cere [ 10/Oct/17 ] |
| Comment by Tim Rozet [ 12/Oct/17 ] |
|
Thanks Tomas. Can this be backported to nitrogen and carbon please? |
| Comment by Tomas Cere [ 13/Oct/17 ] |
|
nitrogen: carbon will have to wait as it has some conflciting stuff(blueprint migration i guess) and I dont have the bandwidth for it atm. |
| Comment by Tomas Cere [ 25/Oct/17 ] |