Feature request/configuration model

[AThums]

Feature request for issue #2357 as discussed in https://github.com/orgs/eclipse-score/discussions/472#discussioncomment-14990332
Goals is to discuss and acceüt this feature request in F2F meeting in Jan

[github-actions]

⚠️ Docs-as-Code version mismatch detected
Please check the CI build logs for details and align the documentation version with the Bazel dependency.

[masc2023]

Feature request does not follow Process, needs to use https://github.com/eclipse-score/score/blob/main/.github/ISSUE_TEMPLATE/3-change.yml

Compare also https://eclipse-score.github.io/score/main/contribute/contribution_request/index.html
and especially
https://eclipse-score.github.io/score/main/platform_management_plan/change_management.html#doc__platform_change_management_plan

[AThums]

Feature request does not follow Process, needs to use https://github.com/eclipse-score/score/blob/main/.github/ISSUE_TEMPLATE/3-change.yml

Compare also https://eclipse-score.github.io/score/main/contribute/contribution_request/index.html and especially https://eclipse-score.github.io/score/main/platform_management_plan/change_management.html#doc__platform_change_management_plan

Issue #2357 following template created and linked

[masc2023]

Linked the PR to the ISSUE, so that it follows the Process,now

[github-actions]

The created documentation from the pull request is available at: docu-html

[AThums]

Linked the PR to the ISSUE, so that it follows the Process,now

issue linked

[AThums]

re-opend to merge

[AThums]

@ramceb : As we were also interested in this topic, can you please give feedback on the content. Thanks, Andreas

[ramceb]

@AThums: Thanks for driving this. Content-wise this goes in the right direction. 5 cents from my side. Sorry for the loose collection of thoughts.

• the configuration of applications shall be self-contained. This makes testing etc much easier as there are no implicit assumptions on the environment. e.g. an application shall desribe how it wants to be supervised.

• applications shall describe their assumed and guaranteed capabilities. What they need from their enviroment and what they provide to the environment. Capabilities can be: secpol/selinux config, provided and required services, filesystem access, any other resources etc. out of this we can derive then dependencies.

• the software platform shall take care at startup if it can fulfill the needs of an application or not.

• any configuration parameter shall have a direct impact on the behavior of the platform.

• if we have applications depending on each other, we shall assume that they are developed based on similar application framework, which shall provide consistency checking accross applications.