From ce69cbe8ece2caf0295254da48f23ec87685f9d4 Mon Sep 17 00:00:00 2001 From: Ana <84312885+AnaLoznianu@users.noreply.github.com> Date: Wed, 25 Oct 2023 18:24:09 +0300 Subject: [PATCH] Update developers/compute-to-data/compute-workflow.md Co-authored-by: Alex Coseru --- developers/compute-to-data/compute-workflow.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/developers/compute-to-data/compute-workflow.md b/developers/compute-to-data/compute-workflow.md index 90386334..391fa897 100644 --- a/developers/compute-to-data/compute-workflow.md +++ b/developers/compute-to-data/compute-workflow.md @@ -27,7 +27,7 @@ The consumer selects a preferred environment from the provider's list and initia 10. After volume creation and allocation, the operator engine starts "pod-configuration" as a new pod in the cluster. ## Loading Assets and Algorithms -11. The pod configuration requires the data asset and algorithm, prompting a request to the provider for retrieval. +11. Pod-configuration requests the necessary data asset(s) and algorithm from their respective providers. 12. The provider uploads assets to the allocated job volume. 13. Upon completion of file uploads, the provider notifies the pod configuration that the assets are ready for the job. 14. The pod configuration informs the operator engine that it's ready to start the job.