-
Notifications
You must be signed in to change notification settings - Fork 93
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
Migrate "rose suite-run" functionality into cylc. #1885
Labels
Comments
Closed
[meeting] we agreed:
Not clear yet, possibly later:
Need to consider the issues raised in #1720 |
This was referenced Jun 19, 2016
See metomi/rose#1536 |
11 tasks
7 tasks
4 tasks
I have started to discuss plans for this meta-ticket in cylc-admin... |
11 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Cylc still uses its original simplistic run-in-place model: the user registers a suite source location and cylc loads it from that location (repeatedly, for reruns, restarts, reloads), This can be a problem if changes need to be made while the suite is running: users have to manage the distinction between source and live/running suite definitions manually, or else be very careful about working in-place.
rose suite-run
was created largely to get around the limitations of this model by automatically separating source and installed suites, and we agreed some time ago to move its main funcitionality over to cylc in due course.Accordingly, the new cylc suite-run command (see #1030) should:
Ideally the new cylc suite-run command should also have the ability to install files from external locations, because almost any suite needs that, but this may need some discussion because it is somewhat tied to rose suite and app configuration functionality, which cylc won't be taking.
The text was updated successfully, but these errors were encountered: