The autotest server needs to execute a bunch of a commands on a test client for a typical job; each one of those commands needs to wait on a costly authentication process.
Fortunately, SSH does have mechanisms to make subsequent ssh sessions to use a master connection if available. Search for ControlMaster in http://www.openbsd.org/cgi-bin/man.cgi?query=ssh&sektion=1 What's even better, the support for Master SSH connection already exists in autotest, only that it is turned off by default. What I am proposing here is that we turn this on so people can benefit from the speed boost on jobs executed from an autotest server, without even thinking about it. We believe most of the scenarios involving installing an autotest server use distros sufficiently recent to support the MasterControl feature. Signed-off-by: Lucas Meneghel Rodrigues <[email protected]> --- global_config.ini | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/global_config.ini b/global_config.ini index 33f2b28..5ca2612 100644 --- a/global_config.ini +++ b/global_config.ini @@ -181,7 +181,7 @@ hours_to_wait_for_recovery: 2.5 # SSH implementation used by autoserv (raw_ssh or paramiko) ssh_engine: raw_ssh # Enable OpenSSH connection sharing. Only useful if ssh_engine is 'raw_ssh' -enable_master_ssh: False +enable_master_ssh: True # Fix problems originated from logging + threading inside autotest require_atfork_module: False # Set to False to disable ssh-agent usage with paramiko -- 1.7.10.2 _______________________________________________ Autotest mailing list [email protected] http://test.kernel.org/cgi-bin/mailman/listinfo/autotest
