Contains all the packaging tools used so far.

Contact: Haiyan Meng, University of Notre Dame

1. git clone git://github.com/cooperative-computing-lab/cctools.git cctools-src
2. cd cctools-src
3. ./configure --prefix $HOME/cctools
4. make
5. make install
6. export PATH=$HOME/cctools/bin:$PATH

1. cd $HOME
2. git clone https://github.com/SISC2014/provenance-tools.git
3. export PATH=$HOME/provenance-tools/cctools/bin:$PATH

#Run your desired program inside of parrot, giving options to record the files accessed parrot_run --name-list my.namelist --env-list my.envlist

More details at http://ccl.cse.nd.edu/software/autobuild-doc/man/parrot_run.html

#Package up the files mentioned in the namelist parrot_package_create --name-list my.namelist --env-list my.envlist --package-path my.package

More details at http://ccl.cse.nd.edu/software/autobuild-doc/man/parrot_package_create.html

#Now, my.package contains a complete filesystem sufficient to run the original command.It is just a plain filesystem tree, so you can edit and add/remove files as needed.To re-run it, you need a tool that can provide the modified namespace.We provide tools to do that with parrot or chroot, but docker or vms are also possible

parrot_package_run --package-path my.package

(or)

chroot_package_run --package-path my.package

More details at http://ccl.cse.nd.edu/software/autobuild-doc/man/parrot_package_run.html More details at http://ccl.cse.nd.edu/software/autobuild-doc/man/chroot_package_run.html

Contact: Tanu Malik, Quan Pham, University of Chicago

1. cd $HOME
2. git clone https://github.com/SISC2014/provenance-tools.git
3. export PTU_HOME=$HOME/provenance-tools/ptu
4. export PATH=$PATH:$PTU_HOME

#In capture/audit phase, prepend ptu before the actual execution command of the application to capture and create the package ptu [-v for verbose ouput; -o for custom output location]

#Above step results in cde-package folder. It consists of all the captured files and the file system cd cde-package

#For re-execution, cde.log contains the execution steps of the application as a shell script ./cde.log

NOTE: Change the permissions of cde.log if not done. chmod +x cde.log