Add Spack buildcache to CPU Ubuntu builds

[cameronrutherford]

Merge request type

• New feature

Relates to

• Spack configuration
• Other

This MR updates

• Spack configuration
• Other

Summary

Adds buildcache support for ExaGO Spack CPU builds. Should substantially speed up builds, and enable adding more of these builds in the future.

[cameronrutherford]

Good to merge with an approving review.

Note that this has moved our spack CPU build speeds down from 1.5hr to <20 mins

[abhyshr]

Might be better for Jaelyn or Ryan to review this. I am not familiar with this stuff.

[cameronrutherford]

https://asciinema.org/a/KCi5TmUXc6zWDj7JYHzfSFxmw - I need to update docs, but now installing exago based on these buildcaches takes <60 seconds :)

[cameronrutherford]

I took a sweep at the documentation and it 100% needs a review. We should probably replace some of my lazier language with just issue references and get more help cleaning up some of the things that are more out of date.

@jaelynlitz since we are really pushing jupyter tutorials in the future, quarto will be really nice for sustainability, and making things prettier + easier to maintain. I think our pdf is probably extremely out of date in a few respects now.

[cameronrutherford]

@abhyshr take a look at my documentation additions to the branch at least

[ryandanehy]

Not sure this is the place for this comment, but there is a link in the buildsystem readme.md that points to gitlab which of course requires a login. Since this is a public repo should we refrain from linking to gitlab in our docs? It links to an old MR.

[ryandanehy]

Not sure this is the place for this comment, but there is a link in the buildsystem readme.md that points to gitlab which of course requires a login. Since this is a public repo should we refrain from linking to gitlab in our docs? It links to an old MR.

broken link here as well https://github.com/pnnl/ExaGO/blob/spack-ubuntu-cache-dev/buildsystem/spack/README.md

[ryandanehy]

Broken links on this page
https://github.com/pnnl/ExaGO/blob/spack-ubuntu-cache-dev/docs/exago_policy_compatibility.md
We might need to open PR later to deal with the revamp / refresh of the docs

[ryandanehy]

Looks good but does inspire a revamp of the old docs.

[cameronrutherford]

If @jaelynlitz or @ryandanehy can approve (I need a re-review because I rebased), then this will auto merge when the pipeline succeeds

[DJ-pnnl]

I found that there is a 1,000 package limit but I haven't found that in documentation. Currently, ExaGO is the only package this org has though. I'm still looking into adding cleanup to the packages as well. Thanks, DJ From: Cameron Rutherford ***@***.***> Sent: Thursday, November 30, 2023 6:52 PM To: pnnl/ExaGO ***@***.***> Cc: DJ Moore ***@***.***>; Mention ***@***.***> Subject: Re: [pnnl/ExaGO] Add Spack buildcache to CPU Ubuntu builds (PR #85) Check twice before you click! This email originated from outside PNNL. @DJ-pnnl<https://github.com/DJ-pnnl> is there a limit on the number of packages we can have? Do you know of easy ways to clean things out that might be older than n-weeks? - Reply to this email directly, view it on GitHub<#85 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AXARDEFGU4W6KR2RFH6YQRTYHFA6ZAVCNFSM6AAAAAA7VL7PLWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZVGM3TCOBUGY>. You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>