Skip to content

upscaling: doc update #113

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

upscaling: doc update #113

wants to merge 1 commit into from

Conversation

JanssenBrm
Copy link
Contributor

No description provided.

Signed-off-by: JANSSENB <bram.janssen@vito.be>
@JanssenBrm
Copy link
Contributor Author

PR for starting the review on the upscaling documentation

| UPSC-05 | The selected platform should support the provisioning of dedicated compute power and storage service for the upscaling scenario to be executed. For both openEO-based and Application Package-based algorithms, Platform Providers can choose whether to offer this through dedicated capacity or by utilising a large pool of elastic capacity. | Ensuring necessary resources for larger upscaling tasks is crucial. For Application Package-based upscaling, provisioning can include: |
| | | |
| | | * Provisioning of dedicated Cloud processing resources (for instance, Kubernetes dedicated PODs) for the hosting of the algorithm(s) selected by the project for the processing of large-scale geographical areas. |
| | | * Provisioning of dedicated HPC resources when available. For such environments, Toil is the recommended workflow engine optimised for distributed computing environments, enabling the execution of CWL workflows across multiple compute nodes. |
Copy link
Contributor

Choose a reason for hiding this comment

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

Doesn't it go quite far to recommend a workflow engine in requirements that are supposed to be about technology agnostic standards?
If we want to give suggestions on how to achieve the requirements, maybe links to the EOEPCA project can help, because they (are supposed to) maintain documentation on best practices.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants