[RFE] [LBaaS] ssh connection timeout
Bug #1457556 reported by
Kevin Fox
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
octavia |
Invalid
|
Wishlist
|
Unassigned |
Bug Description
In the V2 api, we need a way to tune the lb connection timeouts so that we can have a pool of ssh servers that have long running tcp connections. ssh sessions can last days to weeks and users get grumpy if the session times out if they are in the middle of doing something. Currently the timeouts are tuned to drop connections that are too long running regardless of if there is traffic on the connection or not. This is good for http, but bad for ssh.
tags: | added: lbaas |
tags: | added: rfe |
summary: |
- lbaas ssh connection timeout + [RFE] [LBaaS] ssh connection timeout |
Changed in neutron: | |
milestone: | none → mitaka-1 |
Changed in neutron: | |
milestone: | mitaka-1 → mitaka-2 |
Changed in neutron: | |
milestone: | mitaka-2 → mitaka-3 |
Changed in python-neutronclient: | |
assignee: | nobody → Reedip (reedip-banerjee) |
Changed in neutron: | |
milestone: | none → mitaka-3 |
Changed in neutron: | |
milestone: | mitaka-3 → mitaka-rc1 |
Changed in neutron: | |
milestone: | mitaka-rc1 → newton-1 |
Changed in neutron: | |
milestone: | newton-1 → newton-2 |
Changed in neutron: | |
assignee: | nobody → Reedip (reedip-banerjee) |
status: | Incomplete → In Progress |
Changed in neutron: | |
milestone: | newton-2 → newton-3 |
Changed in neutron: | |
milestone: | newton-3 → newton-rc1 |
Changed in neutron: | |
milestone: | newton-rc1 → none |
status: | In Progress → Incomplete |
Changed in neutron: | |
status: | Incomplete → In Progress |
affects: | neutron → octavia |
affects: | python-neutronclient → python-openstackclient |
Changed in python-openstackclient: | |
status: | Incomplete → New |
assignee: | nobody → Reedip (reedip-banerjee) |
To post a comment you must log in.
please try below solution and see if it can be workaround or not.
1. increase all underlay interfaces MTU, e.g. 9000
or
2. decrease the client and backend servers MTU to less than 1500. e.g. 1450