Persistency CFT [2025-06-05, 2:30 - 4:00 pm]

[guysagnes]

Agenda

Change of Cross Functional Team (CFT) to Functional Team (FT)

Participants:

• @guysagnes
• @sbachmann-qorix
• @joshualicht
• @BogdanBadicu
• @umaucher
• @arsibo

slack communication channel for Persistency FT

• will be initiated by Bogdan Badicu
  -> https://sdvworkinggroup.slack.com/ssb/redirect

Meeting reports

Cross CFT

• The component template from SCORE will handle C++ and Rust in one repository
• Process in scope of pilot process definition inside persistency
  refer to Epic: Process Pilot #760

Architecture

• Baselib will be use as module to allow visibility of the API
  • The implementation of the related component will be assigned to the related FT

Workpackages

Open Pull request
KVS Feature / Requirements
Feature: Persistency KVS - Feature Architecture -> ready for review
Feature: Persistency KVS - Component Requirements -> draft

Architecture / Design

• Improvement: Adaptation of the open / build for KVS to allow process separation #1071

Open actions

• Requirement related safety qualification level (QM / ASIL_B) started @sbachmann-qorix (Pilot)

Meeting Minutes

Related Persistency CFT Board:
Persistency FT

Feature Request for Persistency · Issue #95 · eclipse-score/score

Focus:

• C++ PoC and related deployment proposal fpr C++/ Rust in a single repo
  [Initial Implementation of CPP POC by joshualicht · Pull Request init: update initial links #4 · joshualicht/inc_mw_per]
  (Initial Implementation of CPP POC joshualicht/inc_mw_per#4)
  https://github.com/joshualicht/inc_mw_per/tree/template_refactoring/src

• C++ Code coverage with bazel - see below

• filesystem - baselib defined scope

• kvs: adapted review points in library and tests inc_mw_per#7 - review feedback addressed

• 2nd Walkthrough Architecture: https://eclipse-score.github.io/score/pr-1068/features/persistency/architecture/index.html

  • Finding of the review will be provided to the pull request directly

• Walkthrough Component: https://eclipse-score.github.io/score/pr-1069/features/persistency/requirements/index.html

• Feature Safety Planning https://eclipse-score.github.io/score/pr-1069/features/persistency/safety_planning/index.html

Reference:

• requirements_inspection_checklist
• requirements_templates

Requirement definition

The requirement reported are defined following the template :-)
Requirement Formulation Template

code delivery / documentation update

• https://github.com/eclipse-score/inc_mw_per/pulls
• https://github.com/eclipse-score/score/pulls

[guysagnes]

Persistency feature scope

The persistency feature was removed in context of the pull-request. #1068
The component / module is directly reported under Features - no related to the functional team.
This approach needs to be aligned - Persistency may have still the two initial scope

• key-value storage
• file-system.

feedback

the structure with the visibility of the functional area should be maintained for features as defined in the concept phase. (as aligned with Volker Häussler)

[joshualicht]

template

https://github.com/eclipse-score/module_template

C++ Code Coverage with Bazel

Bazel seems to not have official support for code coverage when used with clang (LLVM). The problem can be solved when using experimental flag: --experimental_generate_llvm_lcov
together with the following environment variables:
BAZEL_USE_LLVM_NATIVE_COVERAGE=1
GCOV={path to llvm_profdata}
CC=clang
BAZEL_LLVM_COV={path to llvm_cov}

(Source of this solution bazelbuild/bazel@21b5eb6)

[guysagnes]

Open action:

• C++ PoC
  Initial Implementation of CPP POC joshualicht/inc_mw_per#4

  • Initial Implementation of CPP POC
    • Set Default Value Handling TBD

• replace common template Rust Cpp
  ->source
  ---> cpp (BUILD)
  ------> inc
  ------> src (may content multiple unit (protected header / cpp files) -
  ---> rust (BUILD)

[guysagnes]

Feature requirement

• Data-change events - feat_req__persistency__events

  • requirement proposed to be removed - the callback notification in local. no use case of it similar to AUTOSAR

• ASync requested in relation to orchestrator
  feat_req__persistency__async_api

• Fast access - to be clarified within architecture community
  feat_req__persistency__fast_access
  Related to stkh_req__execution_model__short_app_cycles

  • This stake holder requirement is non functional and cannot be addressed on generic level.
    The requirement can only be take in account with the realization on system level (incl hardware)

[umaucher]

There is an existing #score-persistency slack channel in the scope of the SDV's slack workspace see https://sdv.eclipse.org/get-engaged/ ... at least @sbachmann-qorix I have seen there already 😉

[sbachmann-qorix]

[like] Sven Bachmann reacted to your message:

…

________________________________ From: Uwe ***@***.***> Sent: Friday, June 6, 2025 1:40:07 PM To: eclipse-score/score ***@***.***> Cc: Sven Bachmann ***@***.***>; Mention ***@***.***> Subject: Re: [eclipse-score/score] Persistency CFT [2025-06-05, 2:30 - 4:00 pm] (Discussion #1193) Caution: This email originated from outside of Qorix. Do not click links or open attachments unless you recognize the sender and know the content is safe. There is an existing #score-persistency<https://sdvworkinggroup.slack.com/archives/C08B339ETQU> slack channel in the scope of the SDV's slack workspace see https://sdv.eclipse.org/get-engaged/ ... at least @sbachmann-qorix<https://github.com/sbachmann-qorix> I have seen there already 😉 — Reply to this email directly, view it on GitHub<#1193 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BQ25FZQA3RNTDMXUGM44ZST3CGK3PAVCNFSM6AAAAAB6SJG7XOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGMZZGA3TIMA>. You are receiving this because you were mentioned.Message ID: ***@***.***>