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
For the MVP, create a minimal platform configuration for the Parallel Works (PW) Azure platform that can be used when running the Launch task. This is possibly non-trivial as it may require a new configuration for each new PW cluster we create. If possible, we may want to consider how to make this more flexible from the outset as well.
Background
Previously, the UFS-RNR software was not designed to be flexibly cross-platform, and we want to design that into rnr-refresh from the outset.
Next Steps
Start with understanding the Cylc 8 Platform Configuration options, and customize it as needed to get the Launch task functioning at a minimum. This platform should probably be configured after the Hera configuration is accomplished, just because it is likely to be more complex. At a minimum, it should work for the Launch task on at least one Azure cluster, and may have to define a new issue to make it more flexible later.
The text was updated successfully, but these errors were encountered:
Description
For the MVP, create a minimal platform configuration for the Parallel Works (PW) Azure platform that can be used when running the Launch task. This is possibly non-trivial as it may require a new configuration for each new PW cluster we create. If possible, we may want to consider how to make this more flexible from the outset as well.
Background
Previously, the UFS-RNR software was not designed to be flexibly cross-platform, and we want to design that into rnr-refresh from the outset.
Next Steps
Start with understanding the Cylc 8 Platform Configuration options, and customize it as needed to get the Launch task functioning at a minimum. This platform should probably be configured after the Hera configuration is accomplished, just because it is likely to be more complex. At a minimum, it should work for the Launch task on at least one Azure cluster, and may have to define a new issue to make it more flexible later.
The text was updated successfully, but these errors were encountered: