VisTrails integration

[remram44]

A VisTrails workflow to execute the experiment once unpacked. Would use CLTools to run the program.

• [ ] Problem: VisTrails doesn't allow packing CLTools definitions in vt bundles (like it does abstraction) filed #875 on VisTrails; unpacker can put the JSON in correct location automatically though.
• [ ] Need to identify input/output files that are on the command-line.
• [ ] Creating a workflow for the "directory" unpacker is easy: it basically has the same information than the bash script.
• [ ] chroot is going to need special support in CLTools
• [ ] vagrant is going to need a specific package
• We probably want to be able to expand a node: when the experiment is a batch script, or if running different commands with --continue, put several CLTools modules.

[remram44]

These points were about running any experiment, once it's been traced/packed/unpacked, into VisTrails.

In addition, Juliana mentions that having tracing integrated in VisTrails could also make sense, so that we can easily restore the environment on a different machine (also VisTrails components?)

[remram44]

Looking at the examples I already tried on reprozip, it is probably common for input and output files not to be directly mentioned on the command line (mc33 has an "input directory" and "file name in input directory"...).