Idea #3699
Updated by Tim Pierce over 9 years ago
Use case: user can copy a pipeline instance between Arvados instances, in order to rerun a pipeline on another cluster and compare results with the original computation. Example: # User runs @arv-copy 1h9kt-pipeline-uuid 1h9kt 4xphq@ to copy instance @1h9kt-pipeline-uuid@ to cluster 4xphq # User views the new pipeline instance on 4xphq's workbench # User clicks "run" on the copied pipeline template page (selecting an appropriate input collection, probably the input collection that was copied along with the pipeline instance and template) # Jobs run. # User uses "compare pipelines" on 4xphq to compare the original, copied 1h9kt pipeline instance with the new 4xphq instance that was just generated. Syntax: <pre> $ arv-copy [--recursive=true/false] [pipeline-instance-uuid] [source-arvados] [destination-arvados] </pre> By default, arv-copy exports the specified pipeline instance from the _source-arvados_ instance and imports it to _destination-arvados_. arv-copy makes removes the following changes to the pipeline instance fields before importing it: * renames @uuid@ them to @properties.copied_from_pipeline_instance_uuid@ the destination Arvados: * removes @owner_uuid@ The @--recursive@ option, which defaults to true, also copies the following data: * collections (copy blocks and then copy manifest_text) * docker images (collection copy + docker specific tags) * pipeline templates (copy name, components) * git repository (clone entire repository; update name of repository to use in components of target pipeline template) If @--recursive=false@, copy only the pipeline instance, but emit a warning that the user will have to fix the pipeline template UUID by hand. arv-copy works only on pipeline instances. It returns an error if _pipeline-instance-uuid_ refers to anything other than a pipeline instance.