-
Notifications
You must be signed in to change notification settings - Fork 60
doc: Add Orchestration feature architecture #1374
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
The created documentation from the pull request is available at: docu-html |
d42858f
to
616e0c2
Compare
This PR is stale because it has been open for 30 days with no activity. It will be closed in 10 days if no further activity occurs. #magic___^_^___line |
Auto-closing: no activity for 30 days. If this is still relevant, reopen or create a fresh PR. |
# | ||
# SPDX-License-Identifier: Apache-2.0 | ||
# ******************************************************************************* | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please use template from templates folder. It shall be a document so that it can be found also in the documentation management plan.
Overview | ||
-------- | ||
|
||
An brief overview of orchestration is described . |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
An brief overview of orchestration is described . | |
An brief overview of orchestration is described. |
- Allows the creation of an application task flow in the `config-by-code` case | ||
|
||
2. **Deployment** | ||
- Provides a way to bind specific application actions to concrete implementations in the current system: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Provides a way to bind specific application actions to concrete implementations in the current system: | |
- Provides a way to bind specific application actions to concrete implementations in the current system |
Or is there a enumeration missing?
- Provides a way to bind specific application actions to concrete implementations in the current system: | ||
- Binding events to Local/Remote/Timers | ||
- Configuring certain threads for callables | ||
- ... |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- ... |
If there are missing elements and they are not defined yet please describe what is missing and will be added.
############# | ||
|
||
.. document:: Orchestration | ||
:id: doc__orch |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
:id: doc__orch | |
:id: doc__orchestration |
:maxdepth: 1 | ||
:glob: | ||
:titlesonly: | ||
:hidden: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a reason why you use hidden? We don't do this in the process description's and I think it's helpful for the orientation.
# SPDX-License-Identifier: Apache-2.0 | ||
# ******************************************************************************* | ||
|
||
Containers Component Architecture |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please use document template for component architecture.
# ******************************************************************************* | ||
|
||
|
||
Containers Component Architecture |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please use document template for component architecture.
# SPDX-License-Identifier: Apache-2.0 | ||
# ******************************************************************************* | ||
|
||
Frontend Architecture |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please use document template for component architecture.
# SPDX-License-Identifier: Apache-2.0 | ||
# ******************************************************************************* | ||
|
||
Frontend Architecture |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please use document template for component architecture.
# ******************************************************************************* | ||
|
||
.. | ||
# ******************************************************************************* |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One copyright header should be enough
# ******************************************************************************* | ||
|
||
.. | ||
# ******************************************************************************* |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please delete one of the copyright header
8650656
to
0a9eadc
Compare
# SPDX-License-Identifier: Apache-2.0 | ||
# ******************************************************************************* | ||
|
||
Frontend Architecture |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same headline as used in runtime lead to same named entries in navigation list
Signed-off-by: Pawel Rutka <pawel.rutka.ext@qorix.ai>
0a9eadc
to
16eec33
Compare
|
No description provided.