A new parameter rpc_response_max_timeout is added and registered into
neutron.conf. (related codes in neutron)
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.
In class _BackingOffContextWrapper, _max_timeout and its setters are
useless temporarily because users can now directly change the rpc_max_
timeout in neutron.conf. However, there're not deleted as we should not
prevent the developer to override this parameter.
Co-Authored-By: Allain Legacy<Allain.legacy@windriver.com>
Change-Id: I45d2e5c063d2dd43cb8aec1d46faa3ee8ea4825f
Depends-on: https://review.openstack.org/#/c/626109
Related-Bug: #1805769
Story: 2004456
Task: 28171
af902dfb2a