f1592c42d9649e8da952021aa1f6e7a4a127cd48

A new parameter rpc_response_max_timeout is added and registered into neutron.conf. The rpc_response_max_timeout plays a role of the ceiling of timeout seconds when waiting for the response of a remote rpc server. During an RPC call, the waiting time starts from the existing parameter rpc_response_timeout(default 60s) and doubled each time until it reaches the ceiling which is currently set as 10 times rpc_response_timeout. It seems to be less flexible since user cannot directly change the ceiling value unless he/she changes the rpc_response_timeout. By adding rpc_response_max_timeout, user can now modify it without changing any other parameters. Co-Authored-By: Allain Legacy<Allain.legacy@windriver.com> Change-Id: I170113c2946cc95308edcb1a703a99c71e50b6f9 Related-Bug: #1805769 Story: 2004456 Task: 28171
Team and repository tags
Welcome!
To learn more about neutron:
- Documentation: https://docs.openstack.org
- Features: https://specs.openstack.org/openstack/neutron-specs
- Defects: https://launchpad.net/neutron
- Release notes: https://docs.openstack.org/releasenotes/neutron/index.html
Get in touch via email. Use [Neutron] in your subject.
To learn how to contribute:
CONTRIBUTING.rst
Description
Languages
Python
99.7%
Shell
0.3%