Skip to content

Remove openmpi from injected modules in deployment#146

Merged
anton-seaice merged 4 commits intomainfrom
rc-2025.08.001
Sep 3, 2025
Merged

Remove openmpi from injected modules in deployment#146
anton-seaice merged 4 commits intomainfrom
rc-2025.08.001

Conversation

@anton-seaice
Copy link
Copy Markdown
Collaborator

@anton-seaice anton-seaice commented Sep 2, 2025 •
edited by github-actions bot
Loading

🚀 The latest prerelease access-om3/pr146-3 at 5fc9d52 is here: #146 (comment) 🚀

@github-actions
Copy link
Copy Markdown

github-actions bot commented Sep 2, 2025

🚀 Attempted to deploy access-om3 Prerelease pr146-1 with commit fdb0f47

🖥️ Gadi Deployment ❌

anton-seaice
anton-seaice commented Sep 2, 2025
View reviewed changes
@github-actions
Copy link
Copy Markdown

github-actions bot commented Sep 2, 2025

🚀 Attempted to deploy access-om3 Prerelease pr146-1 with commit 7a515c6

🖥️ Gadi Deployment ✔️

Usage Instructions

access-om3, defined in ./spack.yaml, will be deployed to Gadi as:

  • 2025.08.001 as a Release (when merged).
  • pr146-1 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr146-1

When using the above modules, the binaries shall be on your $PATH.

For advanced users, this Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/0.22/spack in the access-om3-pr146-1 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

If the above was not what was expected, commit changes to config/versions.json in this PR.

@anton-seaice
Copy link
Copy Markdown
Collaborator Author

anton-seaice commented Sep 2, 2025

This change ensures we use the system module for openmpi and prevents conflicts with payu, as it also loads the openmpi module

(implements a workaround for #143 )

@anton-seaice
Copy link
Copy Markdown
Collaborator Author

anton-seaice commented Sep 2, 2025

@CodeGat - what is the meaning/use of the provenance section in packages.json ? (e.g. i wonder if it should include wombatlie)

@anton-seaice anton-seaice self-assigned this Sep 2, 2025
@CodeGat
Copy link
Copy Markdown
Member

CodeGat commented Sep 3, 2025

Hey @anton-seaice - the .provenance set of packages are packages that are included in the release provenance database - see the 'Model Components' section of https://reporting.access-nri-store.cloud.edu.au/release-provenance/releases/30.

The packages in the .provenance array are also generated as modules, FYI

@anton-seaice
Copy link
Copy Markdown
Collaborator Author

anton-seaice commented Sep 3, 2025

Thanks!

We should definitely include wombatlite then - @dougiesquire , is it just generic tracers, or shoud mocsy be included too

@dougiesquire
Copy link
Copy Markdown
Collaborator

dougiesquire commented Sep 3, 2025

Mocsy too please

@anton-seaice anton-seaice marked this pull request as ready for review September 3, 2025 01:55
@github-actions
Copy link
Copy Markdown

github-actions bot commented Sep 3, 2025

🚀 Attempted to deploy access-om3 Prerelease pr146-2 with commit 5fc9d52

🖥️ Gadi Deployment ✔️

Usage Instructions

access-om3, defined in ./spack.yaml, will be deployed to Gadi as:

  • 2025.08.001 as a Release (when merged).
  • pr146-2 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr146-2

When using the above modules, the binaries shall be on your $PATH.

For advanced users, this Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/0.22/spack in the access-om3-pr146-2 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

If the above was not what was expected, commit changes to config/versions.json in this PR.

@anton-seaice
Copy link
Copy Markdown
Collaborator Author

anton-seaice commented Sep 3, 2025

@dougiesquire - can you review please ? No code changes - just changes which modules are exported

dougiesquire
dougiesquire approved these changes Sep 3, 2025
View reviewed changes
Copy link
Copy Markdown
Collaborator

@dougiesquire dougiesquire left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @anton-seaice - LGTM

aidanheerdegen
aidanheerdegen approved these changes Sep 3, 2025
View reviewed changes
Copy link
Copy Markdown
Member

@aidanheerdegen aidanheerdegen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

CodeGat
CodeGat approved these changes Sep 3, 2025
View reviewed changes
Copy link
Copy Markdown
Member

@CodeGat CodeGat left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just adding to a chorus of ticks

@github-actions
Copy link
Copy Markdown

github-actions bot commented Sep 3, 2025

🚀 Attempted to deploy access-om3 Prerelease pr146-3 with commit 5fc9d52

🖥️ Gadi Deployment ✔️

Usage Instructions

access-om3, defined in ./spack.yaml, will be deployed to Gadi as:

  • 2025.08.001 as a Release (when merged).
  • pr146-3 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr146-3

When using the above modules, the binaries shall be on your $PATH.

For advanced users, this Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/0.22/spack in the access-om3-pr146-3 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

If the above was not what was expected, commit changes to config/versions.json in this PR.

@anton-seaice
Copy link
Copy Markdown
Collaborator Author

anton-seaice commented Sep 3, 2025

Thanks for the chorus of agreement !

@anton-seaice anton-seaice merged commit 7439c61 into main Sep 3, 2025
20 checks passed
@anton-seaice anton-seaice deleted the rc-2025.08.001 branch September 3, 2025 03:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@aidanheerdegen aidanheerdegen aidanheerdegen approved these changes

@dougiesquire dougiesquire dougiesquire approved these changes

@CodeGat CodeGat CodeGat approved these changes

Assignees

@anton-seaice anton-seaice

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@anton-seaice @CodeGat @dougiesquire @aidanheerdegen