Conductor is a component in OTS Worker. Basically it does three things:
Conductor has got a command line interface. It can be used to manually execute one or more test packages from Worker PC. In this case, sending test results to OTS server is disabled. The test results are collected to a local folder (~/conductor/None) from where the user can examine them.
Here's an example how to process two test packages using Conductor on command line:
# sudo conductor -u http://my.build.host/image --dontflash -t mypackage1-tests,mypackage2-tests
The option -u in above command is ignored.
Custom Flasher is a component used by Conductor to set up and prepare the test target for the test execution from Worker PC. Typically this includes flashing the software image to hardware that is serving as the test target, and then booting up the hardware.
The user must implement his/her own Custom Flasher for Conductor to be able to prepare the test target.
If Custom Flasher is not available in Worker PC, Conductor skips the phase of preparing the test target. This usually leads to error when Conductor tries to access the test target.
The user must implement Python module customflasher and have it available in PYTHONPATH in Worker PC. In that module, the user can define all the steps and maneuvers that are necessary before his/her test target is ready for test execution. Currently this implies that establishing an SSH connection from Worker PC to the test target must succeed.
Conductor source code includes a reference implementation for customflasher in defaultflasher.py file.