Configuration updates for discover-scu17

[ashley314]

Description

Configuration changes for discover-scu17 for spack-stack 2.0.0

• removes compilers.yaml
• updates packages_oneapi.yaml
• removes packages_intel.yaml

Dependencies

Part of the spack-stack v2 release (or after)

Issues addressed

NA

Applications affected

List all known applications (UFS WM, JEDI, SRW, etc.) intentionally or unintentionally affected by this PR.

Systems affected

List all systems intentionally or unintentionally affected by this PR.

Testing

• CI: Note whether the automatic tests (GitHub actions tests that run automatically for every commit) pass or not
  • GitHub actions CI tests pass
  • GitHub actions CI tests do not pass (provide explanation)
  • GitHub actions CI tests skipped (provide explanation if necessary)
• New tests added: List and describe any new tests added to GitHub actions
  • ...
• Additional testing: Add information on any additional tests conducted
  • ...

Checklist

• This PR addresses one issue/problem/enhancement or has a very good reason for not doing so.
• These changes have been tested on the affected systems and applications.
• All dependency PRs/issues have been resolved and this PR can be merged.
• All necessary updates to the documentation on readthedocs are included in this PR
  • For site config updates, check in particular doc/source/PreConfiguredSites.rst and doc/source/MaintainersSection.rst
• All necessary updates to the spack-stack wiki will be made when this PR is merged

[climbfuji]

@ashley314 Is this ready? It's still a draft. Thanks!

[ashley314]

@ashley314 Is this ready? It's still a draft. Thanks!

Still testing JEDI with these installs on discover. But if something needs to change I can open a new PR. Thanks!

[climbfuji]

@ashley314 While we are waiting for @eap's review, would you be able to pull in the updates from release/2.0 and also update the submodule pointer for spack-packages (repos/builtin) to JCSDA/spack-packages@97141f4 ?

[ashley314]

@climbfuji Done.... I think... you might want to double check this. Thanks!

[climbfuji]

@climbfuji Done.... I think... you might want to double check this. Thanks!

Thanks, the submodule pointer now looks ok. I realized that you started from develop, therefore you now have a change of the top-level README.md from develop for the release branch. This doesn't hurt, in fact it's probably better to have this in the release branch, too. Thus, all good.

[climbfuji]

@ashley314 I'll go ahead and merge. If @eap has additional updates or wants changes to this, we can add those later this week or on Monday before we publish the release. Thanks for the updates!