docs: added orchestration feature request #1293
Merged
Conversation
This file contains hidden or 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
|
The created documentation from the pull request is available at: docu-html |
armin-acn
reviewed
Jul 1, 2025
armin-acn
reviewed
Jul 1, 2025
qor-lb
force-pushed
the
lb_runtime_feature_request
branch
from
a979f76 to
8cf9e98
Compare
ramceb
reviewed
Jul 17, 2025
|
|
||
| To address these challenges, this proposal introduces two frameworks: | ||
|
|
||
| 1. The **Executor**, which provides cooperative, user-space multitasking on top of a configurable thread pool. |
Contributor
There was a problem hiding this comment.
Suggested change
| 1. The **Executor**, which provides cooperative, user-space multitasking on top of a configurable thread pool. | |
| 1. The **:term:`Executor`**, which provides cooperative, user-space multitasking on top of a configurable thread pool. |
Would be great to have this in the glossary
| To address these challenges, this proposal introduces two frameworks: | ||
|
|
||
| 1. The **Executor**, which provides cooperative, user-space multitasking on top of a configurable thread pool. | ||
| 2. The **Orchestrator**, which provides a declarative layer to define execution structures and timing requirements in a way that is independent of the deployment platform. |
Contributor
There was a problem hiding this comment.
Suggested change
| 2. The **Orchestrator**, which provides a declarative layer to define execution structures and timing requirements in a way that is independent of the deployment platform. | |
| 2. The **:term:`Orchestrator`**, which provides a declarative layer to define execution structures and timing requirements in a way that is independent of the deployment platform. |
ramceb
approved these changes
Jul 17, 2025
Contributor
ramceb
left a comment
ramceb
left a comment
There was a problem hiding this comment.
We can merge this for now. But before we go into implementation I would really like to see how a implementation of this FR would fit together with the FEO implementation.
armin-acn
approved these changes
Jul 21, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
closes: #273
clean continuation of #857