You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Before carrying out cylc-flow ticket #3260 get as much agreement as possible on the content of the new cylc-flow.rc.
Background
Before to #2199 (redefining how Cylc submits jobs to compute resources/clusters) we should consider the design of the .rc settings files.
The most logical way to support installation of suites on suite clusters and
job hosts is to migrate our host-based configuration logic to a cluster-based
configuration logic. Some points to consider:
Deprecate global.rc[hosts] section in favour of a [job platforms]
section. The new section should allow us to configure:
Login hosts.
Batch system or workload manager, and related settings.
Deprecate suite.rc relevant settings under [runtime][__MANY__], but have
a top level [job platforms] section that simply mirrors that of global.rc to allow individual suites to override the site/user settings.
Users will configure tasks to run on clusters instead of hosts/batch systems.
If relevant, improve alignment with DRMAA Open Grid Forum API?
So, for example, a suite flow.rc might look like this:
Ideally the suite.rc and the global.rc should be replaced by a single configuration, probably called cylc-flow.rc. It is envisaged that some of it's settings are more likely to be set in a global context, and some in a suite context, but the same settings should be available in both cases.
The text was updated successfully, but these errors were encountered:
Reference #44
Aim
Before carrying out cylc-flow ticket #3260 get as much agreement as possible on the content of the new
cylc-flow.rc
.Background
Before to #2199 (redefining how Cylc submits jobs to compute resources/clusters) we should consider the design of the .rc settings files.
The most logical way to support installation of suites on suite clusters and
job hosts is to migrate our host-based configuration logic to a cluster-based
configuration logic. Some points to consider:
global.rc
[hosts]
section in favour of a[job platforms]
section. The new section should allow us to configure:
suite.rc
relevant settings under[runtime][__MANY__]
, but havea top level
[job platforms]
section that simply mirrors that ofglobal.rc
to allow individual suites to override the site/user settings.So, for example, a suite
flow.rc
might look like this:Ideally the
suite.rc
and theglobal.rc
should be replaced by a single configuration, probably calledcylc-flow.rc
. It is envisaged that some of it's settings are more likely to be set in a global context, and some in a suite context, but the same settings should be available in both cases.The text was updated successfully, but these errors were encountered: