Creating VMs for use as disposable clients is but one piece of the puzzle for disposable clients. We also need to modify how libtaskotron works in order to utilize those VMs.
This will involve (at a minimum, subtasks will be a more complete list): reworking the runner to have one or more subclasses to handle the remote case while maintaining the local execution use case getting required task files onto the remote VM executing task on the remote machine handling any errors during task execution * retrieving all required data off remote machine as artifacts
This ticket had assigned some Differential requests: D356
Merged in disposable-develop as rLTRN7344502fb1c14e0d740673e2af4de43a7d4b5798
Metadata Update from @tflink: - Issue marked as depending on: #228
Login to comment on this ticket.