Persistency CFT [2025-07-10, 3:00 - 4:00 pm]

[guysagnes]

Agenda

Propose to start a short meeting at 15.00 (CEST)

Participants

@guysagnes
@vbogdanb
@joshualicht
@umaucher
@vinodreddy-g
@Ahmed-Elsaka-JC

Feedback Workshop

• Architecture Community F2F Workshop [2025-07-08 - 2025-07-10] #1247
  Architecture Community F2F Workshop [2025-07-08 - 2025-07-10]

  • https://github.com/orgs/eclipse-score/discussions/1247

• Priority for the SCORE Release V0.5

• Dependency from/to other features

  • uses Persistency
    • Feature Request for Deterministic App Abstraction Layer (DAAL) #864 (FEO & DAAL)
    • Feature Request for Config Management #754
    • Feature Request for Diagnostic Services & Fault Management #911
  • dependency for Persistency
    • Feature Request for Health & Lifecycle #909
    • Feature Request for Security & Crypto #905

Team Feedback

• Pull Requests
  • https://github.com/eclipse-score/inc_mw_per/pulls?q=is%3Apr+is%3Aclosed
• Open actions
  • https://github.com/eclipse-score/inc_mw_per/pulls

TL / Arch Meeting Feedback

• no meeting took place this week

[guysagnes]

Priority for the SCORE Release V0.5

• Identification of the gaps analysis for V0.5 by end of the year
• Target is to assessment for the safety
• Expected create a workstream to allow reuse for the safety concept on different modules
  • Action will start by 14.07.2025
  • Identification of AoU (Assumption of Use) for the OS
• Setup reference integration team to integration 0.5 starts

Until End of 2025 - Safety Qualified Release V 0.5

• QNX 8.0
  • demonstrate that SeeoC is managed
  • The architecture can be qualified independently from qualified compiler
    • The artifact can only be provided based on the experimental Rust, but not part of the release
    • Only the C++ Certified stack is currently in first priority expected
  • issue: no qualified Rust Compiler for QNX - risk addressed and under mitigation
    • Possibility to limit the scope only to the C++ component
  • An integration team will be setup

SCORE V0.5 Release Candidate under QNX 8.0 (Focus on C++)

• Linux only
  • focus only on functionality
  • include the Rust component and implementation
• Looking for contribution to create assumption of use (AoU) as part of 0.5 scope (which assumptions an OS would have?!)

[guysagnes]

Requirement adaptation

• KVS the Thread safe aspect is not raised as mandatory - related to the feature requirement

Initial requirement

.. feat_req:: Thread Safety
🆔 FEAT_REQ__KVS__thread_safety
:reqtype: Functional
:security: no
:safety: ASIL_B
:satisfies: STKH_REQ__350
:status: valid

The key-value storage shall allow thread safe access per key.

The proposition is related to

• Performance improvement
• Deadlock on semaphore inside the KVS

Bogdan: Proposition no thread safety if single thread.
Vinod: the created KVS object based on KVS-Builder - single thread or multi thread support - It is a runtime decision
Uwe: Provide a feature flag, not expected - it will result on complexity

• Joshua: propose to evaluate impact for the Mutex access - google bench mark. (supported by Uwe)

API is providing the async access - impose the usage of thread safety

Decision: to allow the configuration of the thread safety.
The configuration can be decided at runtime, the default configuration is active thread safe.

[guysagnes]

Support of the primitive types missing

• missing number types support in context of API - Only number (64)support - conversion imposed

Extension of the API to be prepared in Rust / C++ to allow support of identified primitive type - may be related to the ABI Types.

• create a API extension request identified in the gap analysis context @guysagnes