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

Multi-Supercomputer-Proof Generic Workflows #121

Open
CodeGat opened this issue Sep 13, 2024 · 0 comments
Open

Multi-Supercomputer-Proof Generic Workflows #121

CodeGat opened this issue Sep 13, 2024 · 0 comments
Assignees
Labels
priority:medium type:enhancement Improvements to existing features version:MINOR Doesn't require update to Model Deployment Repositories

Comments

@CodeGat
Copy link
Member

CodeGat commented Sep 13, 2024

See https://github.com/ACCESS-NRI/build-cd/pull/111/files/a34bb0b53657f169450c8ac31a9c3463c9837567#r1758047493 and https://github.com/ACCESS-NRI/build-cd/pull/111/files/a34bb0b53657f169450c8ac31a9c3463c9837567#r1758181572

We have gone quite far in making this repo able to handle multiple supercomputer targets, but we aren't 100% there yet. Things like comment explicitly referring to Gadi, explicit paths to /g/data/vk83/... in comments, among other things.

Audit this repositories use matrices, comments and targets to make sure we can deploy to another supercomputer target as easily as possible.

One main issue is the GitHub Release - matrixing could lead to multiple releases of the same version of a model, with different spack.locks for different targets.

@CodeGat CodeGat added priority:low type:enhancement Improvements to existing features labels Sep 13, 2024
@CodeGat CodeGat self-assigned this Sep 13, 2024
@CodeGat CodeGat added priority:medium version:MINOR Doesn't require update to Model Deployment Repositories and removed priority:low labels Dec 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority:medium type:enhancement Improvements to existing features version:MINOR Doesn't require update to Model Deployment Repositories
Projects
None yet
Development

No branches or pull requests

1 participant