Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Explain output hierarchy when dataspaces are used #286

Open
lpellegr opened this issue Jul 12, 2016 · 0 comments
Open

Explain output hierarchy when dataspaces are used #286

lpellegr opened this issue Jul 12, 2016 · 0 comments

Comments

@lpellegr
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant