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

[guysagnes]

Agenda

Participants:
@guysagnes
@sbachmann-qorix
@joshualicht
@hbragge
@JannikSzwajczyk
@umaucher
@arsibo

Open Pull request

• kvs: adapted review points in library and tests by sbachmann-qorix · Pull Request #7 · eclipse-score/inc_mw_per
  → Review pending (Has Default check) Persistency CFT [2025-04-24, 2:30 - 4:00 pm] · eclipse-score · Discussion #958
  → Rebased requested

• kvs_cpp: Initial cpp interface by vbogdanb · Pull Request #8 · eclipse-score/inc_mw_per
  → Rework requested
  → Reorganization Source
  → dependency to BMW Result class -
  → Adaptation of implementation
  constructor vs. open

Merged content

• fix problem with bazel registry by dcalavrezo-qorix · Pull Request #10 · eclipse-score/inc_mw_per
• Initial Implementation of the KVS_Tool by joshualicht · Pull Request #9 · eclipse-score/inc_mw_per
• persistency: added module template by dcalavrezo-qorix · Pull Request #6 · eclipse-score/inc_mw_per

Closed pull request

• Initial GENIVI PCL Wrapper by guysagnes · Pull Request #3 · eclipse-score/inc_mw_per
  This implementation will not be continued and the related pull request will be closed

Architecture / Design

Following the feedback from https://github.com/orgs/eclipse-score/discussions/472?sort=new 28.04.2025
The persistence CFT shall provide a design proposition how to handle the position of the persisted data in file system

• Proposition about persisted data in file system
  • Aspect: separation of data related to the execution process context (s.b.)

Open actions

• Dev. Process handling presentation - Sven
• Check requirement for default values location to be in code
  Both approach are expected based on code and external definition. see -> https://github.com/eclipse-score/score/pull/1027/files#diff-3eb32dedc0c7db93acd3182b3a6d176276b791d42404123362d7616225ca713cR56
• Recheck function kvs::has_default_value (maybe change to is_current_value_default)
• Check module template handling of c++ and rust sources in same repo

Meeting Minutes

Related Persistency CFT Board:
Persistency FT

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

Pull request are open
persistency: Feature request for KVS by LittleHuba · Pull Request #219 · eclipse-score/score
persistency: Feature request for File Access by LittleHuba · Pull Request #220 · eclipse-score/score

New pull requests:
https://github.com/eclipse-score/score/pull/1027/files
Proposition to check the content from previous commit related to the KVS Feature

• address scope of file system persistence priority due to missing statement for assumption of use spec. QNX inside Lead Community @guysagnes

• Alignment of the board in relation to report https://github.com/orgs/eclipse-score/discussions/853

Next Steps

refer to the board

• Feature review
• Feedback
  • Security / Architecture community
  • File System / Lead community

[guysagnes]

Architecture / Design

Following the feedback from https://github.com/orgs/eclipse-score/discussions/472?sort=new 28.04.2025
The persistence CFT shall provide a design proposition how to handle the position of the persisted data in file system

Proposition about persisted data in file system
Aspect: separation of data related to the execution process context

[guysagnes]

Proposition alignment inside Continental -

Review Architecture Community

Information shared inside Architecture Community session
The important aspect is the relation between executed process and related folder in file system.
This relation has to be defined in a way that a process can be restarted and the same data are linked and used.
Alternative the name of the unique process name is provide to KVS during initialization.

[guysagnes]

• Create Action to allow adaptation of the open / build for KVS to allow process separation @guysagnes
• Address security definition / abstraction to the architecture community @guysagnes

[sbachmann-qorix]

Current process state: 20250508 Qorix Sprint Review KVS.pdf