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

Need MET, METPLUS and a Python environment to support Global workflow #448

Closed
arunchawla-NOAA opened this issue Jan 20, 2023 · 3 comments · Fixed by #454
Closed

Need MET, METPLUS and a Python environment to support Global workflow #448

arunchawla-NOAA opened this issue Jan 20, 2023 · 3 comments · Fixed by #454
Assignees

Comments

@arunchawla-NOAA
Copy link

Please describe the package or library you would like to add to spack-stack.

Global workflow needs MET v9.1.3 and METplus v3.1.1 installed so they can complete verification tasks. They also need a gfs python virtual environment with the following python packages

  • cftime
    • Cython
    • numpy
    • pandas
    • python-dateutil
    • h5py
    • netcdf4
    • PyYAML
    • Jinja2
    • f90nml
    • cartopy
    • matplotlib

What applications will be using this package or library?

This will be used by GFS developers

Is there already a package or library in spack-stack that provides this, or related, functionality?

I do not know if any of these packages have already been added to spack

Additional context
Add any other context or screenshots about the package or library here.

Will This Package be Needed in a NOAA Operational Application?

These packages are already approved on WCOSS

WCOSS System Software Request Checklist

General questions:

Supervisor or sponsor of the requester

Software name and version, specific URL to the software

Software type - New or Upgrade existing?

Justification ( List NPS models using the software)

Completion Time requested

Software License including all Dependency Software Licenses 

Support contact(s) who must have a WCOSS account

Dependency Software list

Installation instructions

Test and verification instructions

Technical Review Checklist for open source software - Review the source code to answer the following questions

Licenses for the requested software and its dependencies

Licenses -  confirm the software Licenses are acceptable

Maturity

Acceptable - Stable, production, or equivalent

Self-contained

No external http, https,  ftp, or other URI exists except that in comments

No binary files in the package unless they are in the approved list

No publicly disclosed cybersecurity vulnerabilities and exposures 

Searching https://cve.mitre.org/cve/

Security High Level Checklists 

Is it prohibited by DHS/DOC/NOAA/NWS

Is it provided by a trusted source? Trusted sources include other NWS, NOAA, or DOC, agencies, or other Federal agencies that operate at a FISMA high or equivalent level. Additionally, trusted sources could be third-party agencies through which there is an existing SLA on file (such as RedHat). 

Is software support offered (is it being updated and patched). 

If maintained by a private entity, does the entity operate in a foreign country, especially a prohibited foreign country (China, Russia, Iran, North Korea, etc.). 

Is there sufficient documentation to support maintenance 

Are there known vulnerabilities or weaknesses

Is there a need for privileged processes 

Are there software dependencies, are those dependencies approved or do they have any security concerns 

Are there any other concerns related to SA, SI, and SC control families

@climbfuji
Copy link
Collaborator

@arunchawla-NOAA All of these packages exist in spack-stack, and we also have a global workflow environment/template. We'll need to check if that environment contains everything in your list, and if the versions match.

@arunchawla-NOAA
Copy link
Author

@WalterKolczynski-NOAA @KateFriedman-NOAA and @aerorahul

Can we move to using spack stack for global workflow ? Do you see any roadblocks there?

@WalterKolczynski-NOAA
Copy link

That's the goal. We need to know where the installations are on each machine though. Other issue is making sure everything is installed under both Intel 18 and Intel 22.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
5 participants