Skip to content

Explain output hierarchy when dataspaces are used #286

@laurentpellegrino

Description

@laurentpellegrino

Let's assume there is a Scheduler running on a machine and a ProActive node deployed on another. A user bobot submits a task that eventually creates a file test.txt on the scratch space of the compute node. If the task was configured to transfer test.txt from the scratch space to:

  • global space, then test.txt is put in defaultglobal/test.txt
  • user space, then test.txt is put in defaultuser/bobot/test.txt
  • output space, then test.txt is put in defaultoutput/bobot/test.txt

This difference of semantic for the output hierarchy between the first and the last two spaces seems to be desired but seems not documented.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions