Config Management FT Weekly #2311

michaelsaborov · 2025-12-09T12:28:17Z

michaelsaborov
Dec 9, 2025
Collaborator

Meeting 13.10.2026

13.10.2026 13:30 - 14:30 CET

Participants

@michaelsaborov
@wei2374
@Chahult
@VictorMorais
@akritisingh1109

rust
- stop-token integration ongoing (in review), no blockers
- rust open-sourcing expected at in the comming 2 weeks CW43-44
QNX build setup for CI
- CI fails because qnx license can´t be accessed, analysis ongoing
- no further CI extenssions planned currently
showcase
- example application to be set in place, precondition is the completed migration to the new mw::service API (WIP)

Meeting 06.10.2026

06.10.2026 13:30 - 14:30 CET

Participants

@michaelsaborov
@wei2374
@Chahult
@VictorMorais
@akritisingh1109

mw::service is open-sourced
CI is re-enabled with ci: fix CI exclusion config_management#68
next steps for the showcase:
- update mw::service API usage
- check real mw::com communication for the showcase based on a static SHM configuration
- check persistency upgrade with mw::storage2
follow-up with reference integration
- update commitId
- coverage, code quality tasks according to description
rust
- stop-token integration under test with CI
- check if CI already supports execution of rust UTs

Meeting 29.09.2026

29.09.2026 13:30 - 14:30 CET

Participants

@michaelsaborov
@wei2374
@Chahult
@akritisingh1109

unit test execution is likely blocked for qnx due to the missing support by baselibs (to be confirmed/clarified):
- baselibs/bazel/unit_tests.bzl at dd1fb40f571e2955b2b14f3bef6ef86ff3f8a374 · eclipse-score/baselibs introduced with eclipse-score/baselibs@91b28d6

Meeting 22.09.2026

22.09.2026 13:30 - 14:30 CET

Participants

@michaelsaborov
@wei2374
@Mahak-085
@akritisingh1109
@Chahult

scenario breakdown for a showcase:
- itf infrastructure will be necessary, working examples are available: add logging demoapp reference_integration#290
- example consists of one executable itf test, 2 demo apps, one passing DLT messages to the other, visible with itf TC (DltWindow())
Calib Plugin planned to be available in Jan/27

Meeting 15.09.2026

15.09.2026 13:30 - 14:30 CET

Participants

@michaelsaborov
@wei2374

scenario breakdown for a showcase:
- ConfigDaemon with Demo Plugin + c++ based example user app (also usable for sctf tests). Pre-requisites:
  - Check availability of SCTF or ITF framework in SCORE sufficient for reference integration showcase with @draganbjedov. Examples available?
  - WIP: mw::service open sourcing
  - mw::com migration complete, based on static configuration config (already in place)
  - demo c++ app based on ConfigProvider lib
mw::com migration
- a CI tool will be necessary to calculate mw::com buffer sizes at build time and generate corresponding config file
- this CI tool will need a normalized file based input with the information about parameter sets and parameter types

Meeting 11.08.2026

11.08.2026 13:30 - 14:30 CET

Participants

@michaelsaborov
@luizcordeiro
@evinoth1206
@wei2374

limited availability during the vacations CW 34 - 36
rust & baselibs: pending PRs are partially merged or need to be rebased, no blockers
mw::com migration: WIP, no blockers

Meeting 28.07.2026

28.07.2026 13:30 - 14:30 CET

Participants

@michaelsaborov
@luizcordeiro
@wei2374

rust rollout strategies
- bazelmod (preferred solution)
  - specific versions of related crates shall be used directly by each client
  - drawback: each client could have different required versions for the same crate, manual agreement is necessary to align each time
- crates.io
  - won´t work because CXX requires a binary, which in turn requires a nightly build tool-chain not available for score
- build manually
  - working option but not the common approach to integrate on crates.io, download all sources necessary at build time (manual handling of what is automated by crates.io)
  - PR available at Add CXX to crates score-crates#57
rust safety considerations (obviously no urgency now to decide about ASIL B qualification)
- local safety certification for each client possible, optimized for a reduced number of required crates
- central safety certification for a "common" set of crates possible (currently a responsibility gap)
- initially rust CfgP could be ASIL QM, since there is no user currently to require an ASIL B
mw::com migration
- shm allocations:
  - client creates a shm ressource for arguments, return vals and related metadata
  - CfgP declares an additional_shm_size of memory of the size of its largest parameter_set (ps_name + payload)
  - within client's allocated shm resource CfgP reserves a memory for parameter_set argument, which is the size of its longest ps_name
  - at the first method call proxy once reserves a buffer for ps_name as argument and server once reserves a buffer for payload as return val. Thus, server needs to know the largest required payload at the first call at latest.
  - statically available communication needs config for params doesn´t contain the information which parameter_sets belong to which clients
  - options:
    - server doesn´t control any usage of payload buffer and takes the risk to be terminated by LoLa in case of buffer overflow. Client can still control the usage of ps_name argument buffer.
    - server assumes the overall largest parameter_set size, this is also used by each client for buffer allocations (inefficient memory usage)
    - client passes its largest parameter_set size as argument of GetParameterSet() method to server (private IPC interface change, transparent for clients). Server doesn´t have to read any size information from the communication needs config.

Meeting 21.07.2026

21.07.2026 13:30 - 14:30 CET

Participants

@michaelsaborov
@luizcordeiro
@wei2374
@Mahak-085

Agenda

libhash score version is now the main development path
rust crates updated for lib result Dependencies for CXX score-crates#54
lib to become part of baselibs: memres, result, libcpp
traceability report (LOBSTER/trlc)
- basic settings done
- TC linkage in progress
- clarification of sphinx-needs requirements template vs trlc ongoing

Meeting 14.07.2026

14.07.2026 13:30 - 14:30 CET

Participants

@michaelsaborov
@luizcordeiro
@wei2374
@Mahak-085

Agenda

release planning
- release v1.0 terms and deadlines:
  - https://eclipse-score.github.io/reference_integration/main/s_core_v_1/roadmap/roadmap.html#status-next-steps
  - https://eclipse-score.github.io/reference_integration/main/s_core_v_1/roadmap/pi4.html
- CalibrationServer is planned to be part of rel v1.0
draft PR with rendered version of TRLC available:
- https://eclipse-score.github.io/config_management/pr-24/config_management_index/index.html based on original contents in https://github.com/eclipse-score/config_management/tree/main/requirements
- next steps: define artifacts needed for the automated safety analysis, resolve formal findings (formating, templates according to sphinx-needs), completion of derivation, TC linkage

Meeting 07.07.2026

07.07.2026 13:30 - 14:30 CET

Participants

@michaelsaborov
@luizcordeiro
@wei2374
@Mahak-085

Agenda

release planning
- definition of release integration process: https://eclipse-score.github.io/reference_integration/main/integration_process/integration_process.html
- possible scenarios for a showcase:
  - ConfigDaemon with Demo Plugin + rust based example user app
  - ConfigDaemon with Demo Plugin + c++ based example user app (also usable for sctf tests)
  - same as above + Calibration Server if available in rel 1.0 (planned)

Meeting 30.06.2026

30.06.2026 13:30 - 14:30 CET

Participants

@michaelsaborov
@luizcordeiro
@wei2374

Agenda

release planning
- v0.8
  - ConfigMgmt: Provide initial set of requirements config_management#14 --> provided with the recent project export to score
  - Set up unit test execution config_management#15 --> unit test config available and working
  - Implement a rust version of config_provider´s API config_management#16 --> in review
- v0.9
  - release integration dry-run -->request placed in the last SCORE tech sync alignement, reponse pending until 06.07.2026
- v1.0
  - clarify the tool environment to be used and migrate if necessary (gcc compiler, testing, coverage, ...) --> gcc12, migration PR feat: upgrade MODULE.bazel to current score cpp toolchain config_management#17 in review, static code analysis tool not available yet
  - 1st offical release (without safety qualification)
additional extensions required for rust: stop_token support and memory ressources implemented, ready for open sourcing

Meeting 23.06.2026

23.06.2026 13:30 - 14:30 CET

Participants

@michaelsaborov
@luizcordeiro
@wei2374

Agenda

release planning
- v0.8
- v0.9
  - release integration dry-run
- v1.0
  - clarify the tool environment to be used and migrate if necessary (gcc compiler, testing, coverage, ...)
  - 1st offical release (without safety qualification)
additional extensions required for rust
- stop_token support (c++ version already exists in baselibs repo: https://github.com/eclipse-score/baselibs/blob/main/score/language/futurecpp/include/score/stop_token.hpp)
- memory ressources (c++ version already exists in baselibs repo: https://github.com/eclipse-score/baselibs/blob/main/score/language/futurecpp/include/score/memory_resource.hpp)

Meeting 16.06.2026

16.06.2026 13:30 - 14:30 CET

Participants

@michaelsaborov
@luizcordeiro
@wei2374

Agenda

dependecies, build
- bug reported to logging: Bugfix: score_logging compile failure - unused variable block_result breaks dependent targets logging#130
- bug reported to baselibs: Deprecated score::StringLiteral causes build failures baselibs#215
- since there is no solution yet proposed for any bug reported, raise fix PRs on our own and let them get approved by code owners
rust support
- buildable version can be made available on score
- further development of runtime features (multithreading) ongoing
mw::POC
- following approach has been confirmed: parameter values are transformed as byte arrays and the whole parameter set sctructure can then be passed over IPC as JSON string of a fixed size. Thus, a pre-estimation of required fixed sized buffer is possible
- to decide whther to use event- or method -based support for IPC

Meeting 12.05.2026

12.05.2026 13:30 - 14:30 CET

Participants

@michaelsaborov
@basheerFZ
@luizcordeiro
@wei2374

Agenda

dependecies, build
- libhash has been committed as part of baselibs, now available vor config_management to verify integrity of parameter data
- Status release v0.7
  - everything is integrated
  - update release notes unclear => follow up today morning => final approval round this afternoon
rust support
- lifecycle integration for rust available
- rust API fo native apps about to be exported to score - coming soon
- rust example application about to be exported to score - coming soon
mw::com POC
- ToDo concept for automatic buffer size calculation, implies replacement of json by flatbuffers (or similar)
- method usage ToDo: an API to inject the calculated size into the buffer allocation at initialization phase to be provided by communication team -> task to be created, mw::service needs method support mechanism for mw::com (blocker)
- event usage ToDo: configuration shall contain bufer size + slot ids, can be provided at build time (at latest at runtime before service initialization)

Meeting 28.04.2026

28.04.2026 13:30 - 14:30 CET

Participants

@michaelsaborov
@basheerFZ
@wei2374

Agenda

build regressions
- external dependencies will hopefully get stableized with release 0.7 and following
- currently manual overrides of particular version are necessary
- clean build on daily basis can´t be ensured at the moment due to this
on 05.05.2026 there will be no participation of @michaelsaborov, @wei2374 and @luizcordeiro due to an internal event

Meeting 21.04.2026

21.04.2026 13:30 - 14:30 CET

Participants

@michaelsaborov
@basheerFZ
@wei2374
@luizcordeiro
@radhe5675

Agenda

build regressions
- build fails for many tragets due to changes in dependent libraries, e.g. version conflicts
- related discussion takes place in Decision record - reference_integration scope #2747 which aims to establish a reference integration and a related process
- our impression is that a reference integration only starts its activities for a dedicated release, not on regular (e.g. daily) basis. Still unclear, how to keep build capability for a given module before a release
- currently it will be hardly feasible to ensure a successful build for config management at any point of time.
- Next steps:
  - try to establish alignment at FT level in regular meetings
  - contact FTs directly and try to find an aggreement there
  - clarify strategy with the release management responsibles

Meeting 14.04.2026

14.04.2026 13:30 - 14:30 CET

Participants

@michaelsaborov
@basheerFZ
@wei2374
@luizcordeiro
@radhe5675
@Mahak-085

Agenda

baselibs to be extended with sha-512 to protect safety related configuration data
- WIP
rust support is going to be provided for native rust apps to interact with ConfigProvider lib
- mw::lifecycle doesn´t support yet execution of native rust apps, to be extended

Meeting 24.03.2026

24.03.2026 13:30 - 14:30 CET

Participants

@michaelsaborov
@basheerFZ
@wei2374
@luizcordeiro
@Mahak-085
@radhe5675

Agenda

CI configuration for config_management in progress: Set ci config for cfg mngmt config_management#5
- initial PR is integrated

Meeting 17.03.2026

17.03.2026 13:30 - 14:30 CET

Participants

@michaelsaborov
@basheerFZ
@wei2374
@luizcordeiro
@Ahmed_Rushdy_Valeo
@VamsiKrishna-max

Agenda

CI configuration for config_management in progress: Set ci config for cfg mngmt config_management#5

Meeting 10.03.2026

10.03.2026 13:30 - 14:30 CET

Participants

@michaelsaborov
@basheerFZ
@wei2374

Agenda

build
- Ensure CfgD and CfgP build in SCORE environment config_management#2 resolved
CI configuration for config_management
- build
- test
- mandatory PR approvals from code owners
- static analysis
requirements engineering
- ongoing

Meeting 03.03.2026

03.03.2026 13:30 - 14:30 CET

Participants

@michaelsaborov
@luizcordeiro
@basheerFZ
@wei2374

Agenda

build
- all build issues completed, update PR in progress and will be pushed soon
- next step: set up CI for a continuous config_management build
- check the applicability of https://github.com/eclipse-score/cicd-workflows
next step: unit testing
- (re-)enable all existing unit tests
requirements mgmt
- update of trlc based req is in progress for
  - Assumed system requirements
  - Feature requirements
  - Component requirements
  - Assumtpions of use
- rendering tool in evaluation to convert trlc to .rst + .html

Meeting 24.02.2026

24.02.2026 13:30 - 14:30 CET

Participants

@michaelsaborov
@luizcordeiro

Agenda

build
- mw::lifecycle issue reported Improvement: Provide mocks for unit testing lifecycle#74, PR Mb add mocks for unit testing lifecycle#78
  fix works, merge still pending
- baselibs::hash opensourcing is in clarification, dependency is removed for now
- mw::com provides a central stubbing

Meeting 17.02.2026

17.02.2026 13:30 - 14:30 CET

Participants

@michaelsaborov
@luizcordeiro
@basheerFZ
@wei2374

Agenda

build
- mw::com message_passing lib interface updated
- mw::com a compiler deprecation warning to be fixed by communication FT, bug report TBD
- mw::lifecycle missing mocks reported as bug Improvement: Provide mocks for unit testing lifecycle#74, fixed, adaptations necessary for target names to match the expectation
- further mw::service stubbing TBD on their side bug report TBD
- hash lib is expected to become part of baselibs
open sourcing of a demo plugin in preparation
set of requirements is supposed to define config management as SEooC. Collaborators are invited to propose requirements from user or implementation perspective:
- AoUs
- Feature req.
- Assumed system req.
- Component req.

Meeting 10.02.2026

10.02.2026 13:30 - 14:30 CET

Participants

@michaelsaborov

Agenda

slack channel is now available for config_management at scoreconfigmanagement.slack.com

Meeting 03.02.2026

03.02.2026 13:30 - 14:30 CET

Participants

@michaelsaborov
@luizcordeiro
@basheerFZ
@wei2374

Agenda

build for CfgD and CfgP. Unresolved dependencies:
- stub in place for mw::service
- in analysis: dependency to datarouter for logging
- mocks needed for mw::lifecycle to enable unit tests, establish contact to FT via https://github.com/orgs/eclipse-score/discussions/2386
- mw::diag should be possible to be removed
- not existing score::hash in baselibs?
- generic_trace_library inside of baselibs or mw::com (?) wrong repo or not existing yet in baselibs
migration / adaption to mw::com
- currently no support for methods and field getter/setter
- draft available for methods: connection of proxy to service could be established successfully. Only fix sized parameters can be used for now
- support for dynamic data types not implemented yet. For now it´s necessary to allocate a fix sized array for a string to get passed.
- to be clarified with communication team how exactly the allocation of memory should work according to the maximal size principle
- no FRANCA model shall be provided for mw::com for configuration, a different format will be supported
- SCTF testing: simpliest TC scenario will work with an empty data base returning an empty result for a GetParameterSet() call. To provide more meaningfull interactions a demo plugin is needed to insert some data into the data model
- new SCTF tests will be necessary, as there will be just a demo plugin available on score
- to be clarified: availability of demo plugin for score

Meeting 27.01.2026

27.01.2026 13:30 - 14:30 CET

Participants

@michaelsaborov
@luizcordeiro
@majehle
@basheerFZ

Agenda

further progress on build for CfgD and CfgP
- json lib dependency adapted and working
- ongoing adaptations for mw::com, mw::lifecycle, mw::service
- communication module will come up with an update to resolve an external dependency issue
general information for newcommers on Config Management feature and next steps
project board set up CFG - Configuration Management FT (view)

Meeting 20.01.2026

20.01.2026 13:30 - 14:30 CET

Participants

@michaelsaborov
@luizcordeiro
@wei2374
@bucci-kawabuchi
@basheerFZ

Agenda

further progress on build for CfgD and CfgP
- since PR has been raised for base libs to fix deprecated result_of API
- stubbing ongoing for mw::com, mw::service
- test existing mw::lifecycle, evtl adapt a mock
requirements management
- requirements linked to unit tests not via numerical ID, but via TRLC ID
- feature level reqs are also maintained primarily in TRLC and get traslated to sphinx needs using a renderer tool
- AoU´s are also maintained in TRLC. Further AoU´s exist as sphinx needs. How do they get synchronized?

Meeting 13.01.2026

13.01.2026 13:30 - 14:30 CET

Participants

@michaelsaborov
@luizcordeiro
@wei2374
@basheerFZ

Agenda

still no commiter permission for config_management repo. Elections vetoed by PMC.
stubbing of missing mw support and score build in progress:
- CfgD approx 30% code + unit tests buildable
- CfgP approx 20% code + unit tests buildable
no objections to the proposal to set up a board for config_mgmt to track the progress. We could work with tasks of a larger granularity in a Kanban style.
requirements management
- no clarity of the process desfinition. There exist different patterns: sphinx needs for feature requirements, trlc for SWC requirements
- analysed the example given by score/mw/com/requirements/component_requirements/component_requirements_ipc.trlc: SWC requirements derived from feature requirements, SWC requirements linked to unit tests via numerical ID
- check the valid and applicable process definition with @antonkri or @aschemmel-tech

Meeting 16.12.2025

16.12.2025 13:30 - 14:30 CET

Participants

@michaelsaborov
@luizcordeiro
@wei2374
@artemmygaiev
@basheerFZ
@FScholPer

Invited but not participated

@buzzdee
@OliverHeilwagen
@darkwisebear
@bucci-kawabuchi
@fabiangierer

Agenda

this meeting invitation is publicly anounced at https://calendar.google.com/calendar/newembed?src=c_2ampi2bmoka3qter4dceap1d5g@group.calendar.google.com&ctz=Europe/Berlin
github repository is set up and available at https://github.com/eclipse-score/config_management/tree/main/score/config_management
still no commiter permission
stubbing of missing mw support and score build in progress
proposal to set up a board for config_mgmt to track the progress like communication: COM - Communication FT (view). All: get familiar with this example and vote in the next meeting.

Meeting 09.12.2025

09.12.2025 13:30 - 14:30 CET

Participants

@michaelsaborov
@luizcordeiro
@wei2374
@fabiangierer
@bucci-kawabuchi
@artemmygaiev

Invited but not participated

@buzzdee
@OliverHeilwagen
@darkwisebear

Agenda

1st regular meeting of FT "Configuration Management"

https://cc-github.bmwgroup.net/oss/eclipse-score-inc_config_management is going to be dismissed and merged to main. Planned to 10.12.2025
commiter permissions not granted yet to any FT member
this meeting has not got anounced on official eclipse calender yet
milestones for configuration management are set up by score project: Configuration Management - S-CORE Release v1.0 #2275
milestones for safety qualification: https://github.com/eclipse-score/score/issues/2277
next steps:
- build config daemon app using stubs for missing mw::services, mw::com
- set up a requirements collection (90% completeness)
- flat buffers POC
this regular meeting will not take place during X-mas vacation period [not on 23.12.2025, 30.12.2025, 06.01.2026]

bucci-kawabuchi · 2026-01-28T11:29:32Z

bucci-kawabuchi
Jan 28, 2026

Hi @michaelsaborov . Apologies for not joining yesterday call.
Just for our status, we are in middle of working on a new release of our product.
Once this is settled soon, we will analyze the config management requirements and bring a draft proposal/idea for alignment to this FT.
Hope that works. Thanks.
Bucci

0 replies

basheerFZ · 2026-02-03T13:37:02Z

basheerFZ
Feb 3, 2026

@michaelsaborov -->Just want to understand based on the above comments as to what type of proposal or idea is expected for collaboration or contribution to this FT.

0 replies

Navigation Menu

Eclipse S-CORE

Config Management FT Weekly #2311

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Replies: 2 comments

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

Eclipse S-CORE

Config Management FT Weekly #2311

Uh oh!

Uh oh!

michaelsaborov Dec 9, 2025 Collaborator

Meeting 13.10.2026

Participants

Meeting 06.10.2026

Participants

Meeting 29.09.2026

Participants

Meeting 22.09.2026

Participants

Meeting 15.09.2026

Participants

Meeting 11.08.2026

Participants

Meeting 28.07.2026

Participants

Meeting 21.07.2026

Participants

Agenda

Meeting 14.07.2026

Participants

Agenda

Meeting 07.07.2026

Participants

Agenda

Meeting 30.06.2026

Participants

Agenda

Meeting 23.06.2026

Participants

Agenda

Meeting 16.06.2026

Participants

Agenda

Meeting 12.05.2026

Participants

Agenda

Meeting 28.04.2026

Participants

Agenda

Meeting 21.04.2026

Participants

Agenda

Meeting 14.04.2026

Participants

Agenda

Meeting 24.03.2026

Participants

Agenda

Meeting 17.03.2026

Participants

Agenda

Meeting 10.03.2026

Participants

Agenda

Meeting 03.03.2026

Participants

Agenda

Meeting 24.02.2026

Participants

Agenda

Meeting 17.02.2026

Participants

Agenda

Meeting 10.02.2026

Participants

Agenda

Meeting 03.02.2026

Participants

Agenda

Meeting 27.01.2026

Participants

Agenda

Meeting 20.01.2026

Participants

Agenda

Meeting 13.01.2026

michaelsaborov
Dec 9, 2025
Collaborator

bucci-kawabuchi
Jan 28, 2026

basheerFZ
Feb 3, 2026