On Thu, Feb 27, 2014 at 5:11 PM, Daniel Manrique < [email protected]> wrote:
> On 14-02-26 12:46 PM, Zygmunt Krynicki wrote: > > > > > Execution controllers > > --------------------- > > > > Execution controllers that prepare the environment for each job would > > necessarily change. Existing set of controllers can run jobs as the > regular > > user, as a root user via sudo or as a root user via > > plainbox-trusted-launcher-1. > > > > In addition to user handing, those controllers handle the task of > configuring > > the filesystem for a specific job. The new remote controller would need > to > > ensure that provider data associated with the job that is to be executed > is > > copied (using rsync or adb push or other similar command). > > This suggests you will copy only relevant data for each test. Can this be > determined reliably without too many hairy heuristics? will we need to add > more > metadata to jobs or scripts so that a remote environment can be properly > configured? > > I don't think we need to add anything, at this time > Another approach that comes to mind is copying *everything* (where > "everything" > needs to be determined) when the first remote job executes, so subsequent > jobs > can count on stuff being there. This would be handled by the execution > controller I think. > > Yes, everything at once. Each time a provider is pulled into the session, all of its data would be copied to the remote device. Thanks ZK
-- Mailing list: https://launchpad.net/~checkbox-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~checkbox-dev More help : https://help.launchpad.net/ListHelp
