feat: armonik domain definitions aep #47
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
qdelamea-aneo
requested changes
Jun 5, 2024
some changes definition of metadata changes Update AEP/aep-0000y.md Co-authored-by: qdelamea-aneo <[email protected]> Update AEP/aep-0000y.md Co-authored-by: qdelamea-aneo <[email protected]> last corrections
italo1aguiar-aneo
force-pushed
the
feat/aep-domain
branch
from
857954a to
1e4a083
Compare
ngruelaneo
reviewed
Jun 6, 2024
|
|
||
| ## Scheduling agent | ||
|
|
||
| Containerized software cohabiting with a worker, running a specific algorithm to determine which tasks its associated workers should perform, scheduling tasks on the workers and monitoring their execution. It also manages all interactions between the worker and the databases (retrieving/saving data, creating new tasks, etc.), as well as managing workers errors and retrying/resubmitting failed tasks when necessary. A scheduling agent, like a worker, exists within a single partition. |
There was a problem hiding this comment.
Suggested change
| Containerized software cohabiting with a worker, running a specific algorithm to determine which tasks its associated workers should perform, scheduling tasks on the workers and monitoring their execution. It also manages all interactions between the worker and the databases (retrieving/saving data, creating new tasks, etc.), as well as managing workers errors and retrying/resubmitting failed tasks when necessary. A scheduling agent, like a worker, exists within a single partition. | |
| Containerized software cohabiting with a worker inside a pod, running the main algorithm of the orchestrator which will determine the tasks that the linked worker will perform. It will schedul the task on the workers and monitor their execution. It also manages all interactions between the worker and the databases (retrieving/saving data, creating new tasks, etc.), as well as managing workers errors and retrying/resubmitting failed tasks when necessary. A scheduling agent, like a worker, exists within a single partition. |
There was a problem hiding this comment.
Maybe we shouldn't use "pod" once we aim to go bare metal soon and it is mostly associated with k3s
|
|
||
| ## Partition | ||
|
|
||
| Logical segmentation of the cluster's pool of machines to distribute workloads according to usage. This feature is provided and handled by ArmoniK. |
There was a problem hiding this comment.
Perhaps we should precise that this the creation is done by Armonik only at deployement stage (for now).
There was a problem hiding this comment.
As it may change soon I think it's better not to give this precision.
|
|
||
| - **Data Dependencies**: Input data for a given task that depends on another unique task. Data dependencies formalize dependencies between tasks. | ||
|
|
||
| - **Expected Outputs**: Data that must be generated as output from a task. If a task submits new tasks then it can transfer responsibility for generating all or part of its outputs to the tasks it submits. |
There was a problem hiding this comment.
Above you are speaking about results, why not use this term here?
There was a problem hiding this comment.
I'm avoiding using the word "results" since we aim to use Blobs from now on. Maybe I could take out the other usage of this word to avoid confusion.
There was a problem hiding this comment.
Following the idea to avoid using the term "result" maybe we should avoid using "data dependencies" but "expected input ids" instead?
Co-authored-by: ngruelaneo <[email protected]>
Co-authored-by: ngruelaneo <[email protected]>
Co-authored-by: ngruelaneo <[email protected]>
Co-authored-by: ngruelaneo <[email protected]>
Co-authored-by: ngruelaneo <[email protected]>
Co-authored-by: ngruelaneo <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.