Uploaded image for project: 'Pegasus'
  1. Pegasus
  2. PM-1545 handling metadata in 5.0
  3. PM-1549

registration of outputs in Pegasus 5.0


    • Type: Icon: Sub-task Sub-task
    • Resolution: Fixed
    • Priority: Icon: Major Major
    • master, 5.0.0
    • Affects Version/s: master
    • Component/s: None
    • None

      Currently in pegasus 4.9 registration gets automatically turned off it the user has not defined pegasus.catalog.replica property

      In 5.0 release we are pushing for zero configuration for users where possible. hence usually the pegasusrc is empty and as a result no registration jobs are created for the workflows.

      One proposal is on table is for us to create a separate output replica catalog in the user submit directory that is different from the input replica catalog. If a user does define pegasus.catalog.replica properties then the user defined will be used for registration.

            vahi Karan Vahi
            vahi Karan Vahi
            4 Start watching this issue