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

Suite UUIDs #439

Closed
hjoliver opened this issue Apr 24, 2013 · 2 comments · Fixed by #2582
Closed

Suite UUIDs #439

hjoliver opened this issue Apr 24, 2013 · 2 comments · Fixed by #2582
Assignees
Labels
Milestone

Comments

@hjoliver hjoliver modified the milestones: soon, later Jun 16, 2016
@hjoliver
Copy link
Member Author

hjoliver commented Jun 16, 2016

[meeting] we agreed suite should pass UUID to tasks, which use it in return comms. Do with comms refactor #1872.

@matthewrmshin
Copy link
Contributor

I propose to do this:

  • cylc run creates a new UUID for a suite, and stores it in the suite runtime database.
  • cylc restart loads the UUID from the suite runtime database.
  • Writes UUID in the suite contact file.
  • Writes UUID in task job environment.
  • cylc message will only send message to suite if the UUID in task job environment is the same as the UUID in the suite contact file.
    • (This is probably good enough. A slightly more complete solution is to have cylc message send the UUID with the message as well, and the suite should reject the message if it is different from its current UUID.)

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

Successfully merging a pull request may close this issue.

3 participants