Missing from MM: Internal compute capacity?

[malloryfreeberg]

We have the following in the FEGA Node Operations Guidelines:

Compute

• Purpose
  • Computing power to ensure that day to day EGA operations can be supported in a timely fashion;
• Features
  • Support ETL pipeline, encryption/decryption, quality assessments, calculations on what is being archived, and a development/testing environment;
• Central EGA adopted solution
  • HPC compute farm and network storage in an isolated part of institutional network only accessible to authorised personnel. Compute resources required depends on submission throughput.

It seems we are missing this from the FEGA MM? I see domains / subdomains for network, security, and storage, but not for computing capacity. This category is important for things like encryption processes, quality assessment, and any other parts of a node's ETL pipeline.

[lauportell]

• Need to add compute capacity for interal porpuses (encryption, quality assessment) in the MM but differenciate it from compute capacity for analysis, which shouldn't be in the model.
• Make it a useful indicator (since it is easy to reach) (TBD)
• Add an intro paragraph to make clear that compute capacity is not for analysis
• Make a draft of how the different levels will look like for the next meeting

[malloryfreeberg]

Subdomain: [4.5] Internal Computing Capacity
Indicator: [4.5.1] Available Computing Capacity
Maturity Levels:

1. No internal computing capacity
2. Internal computing capacity needs are not planned, but sufficient computing resources can be obtained as the node needs
3. A plan to obtain and maintain internal computing capacity required for node services is drafted, considering hosting institution policies and node services required in the Federated EGA ecosystem
4. The Federated EGA Node has a complete and implemented plan to maintain sufficient internal computing capacity for required services and increase capacity when needed
5. Periodic revision of the Internal Computing Capacity Planning according to utilization KPI's of the Federated EGA Node updating it whenever necessary