Versions Compared

Old Version 103

changes.mady.by.user Stephen Lawrence

Saved on

compared with

New Version 133

changes.mady.by.user Stephen Lawrence

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Historical note: the minutes for the previous project, the CVII Tech Stack, can be found here: CVII Technology Stack meeting notes

24th April 2024

Agenda:

  • AMM feedback
  • Team backlog


Minutes:

  • AMM
    • Feedback
      • Paul: Digital.auto came up a few times. Uncertain about what relationship to playground
        • Steve: Personally I see the core digital.auto functionality as being the visual ideation. For that part it could be both a data feeder of VSS data to the playground and a client which uses the playground as a source.
      • Swen: was useful as first time attendee. From CVI discussion yesterday will be sharing mental model of what I perceive as the bigger picture. We need to understand each other to design the right architecture.
      • Haonan: good conference. Good to meet people finally.
      • Steve: Had some interesting conversations in the Showcase with the Playground demo. Some people really got the concept and even talked about using it in their upcoming hackathon. Also had interest from an academic.
    • Thursday workshop
      • Whiteboard:

Image Added

  • Backlog
    • Playground backlog slide from AMM:
      • Next (goal: enhance and use the playground):
        • Review 0.1.0 release and fill obvious doc gaps
        • Socialisation: COVESA groups, Webinars etc.
        • Concrete backlog generation (high lvl points below)
          • Main focus of Thurs Data Architecture team workshop
          • Feeders: VISSR feeder component, RemotiveLabs, etc.
          • Examples: agree data arch team early focus.
          • Connections to COVESA eco-system, e.g. CVI southbound, AOSP northbound
          • Embedded App DB (Realm)
          • DIKW Knowledge layer connector
          • Auto h/w deployment (mid term)
          • Complete project setup: release process etc
  • Discussion in meeting:
    • Need data sets (at rest):
      • VSS data sets (real or simulated)
      • Other data models and rule sets.
    • Next week or two Steve will do some documentation polishing and publish the RemotiveLabs bridge sample code as an example (source is available in his github so ask if you want to know sooner)
    • Discussion of knowledge layer
      • Christian/Haonan are continuing to work on the connector
      • Discussion of rules example Haonan posted to the slack.
      • She explained she's currently bypassing some steps in the processing chain, but is just directly looking at the applicability of processing the timeseries data in RDFox to confirm approaches.

17th April 2024

No meeting due to AMM

10th April 2024

Agenda:

  • 2024 Spring AMM Planning (Data Architecture and Infrastructure)
  • Central Data Service Playground
    • Status reports
    • Release/preview tagging
    • AMM presentation
      • High level near-mid term backlog, e.g:
        • Feeders: VISSR feeder component, RemotiveLabs
        • Examples: agree data arch early focus. see workshop
        • Connections to COVESA eco-system, e.g. CVI southbound, AOSP northbound
        • Embedded App DB (Realm)
        • Knowledge layer connector
        • Auto h/w deployment (mid term)
        • Quality of life improvements: review 0.1.0 release and fill obvious getting-started or doc gaps
        • Agree on and complete project setup: release process, testing etc


Minutes:

  • Spring AMM sessions
  • Central Data Service Playground
    • Status reports
      • Steve:
        • Rebase on upstream VISSR complete and merged.
        • Quality of life Docker Compose improvements (code and doc) complete and merged.
        • Main branch now represents 'playground-core' of 0.1.0 release
        • Current: Now completing IoTDB guide for doc-site (preview here)
        • Next: showcase demo and AMM presentations
    • AMM presentation
      • Agreement on general high level themes for the backlog. Of course list to be actually debated in the workshop
      • Discussion of knowledge layer slides
    • Christian agrees it would be good idea to tag a release.

3rd April 2024

Agenda:


Minutes:

  • Spring AMM sessions
    • Agreement to shorten session on Playground use in favour of discussing it in workshop segment
    • Discussion of workshop topics
      • Steve: add your ideas to the list on the planning page
      • Swen: interested in cloud
      • Christian/Haonan agree to present a few slides to kick-off discussion of knowledge layer
    • Steve has posted a note on LinkedIn advertising the session
  • Central Data Service Playground
    • Status reports
      • Steve has published the Implementation overview page on the doc site.
      • Next steps: point playground to use current upstream VISSR, some clean up and retest, before tagging 0.1.0 release.

27th March 2024

Agenda:

Minutes (retrospective summary):

  • Central Data Service Playground
    • Status reports / Kanban review
      • Steve: Baseline documentation has been published on site. Main content is the logical concept overview. Next will be implementation
      • Steve: Had a look at integrating RemotiveLabs virtual signal platform as a feeder. On hold whilst address issues accessing their cloud system via their CLI through corporate systems.
      • Ulf gave summary of VISSR feeder template
      • Steve: Thanks. I was planning to enable that for IoTDB as part of the backlog.

20th March 2024

Agenda:

  • Spring AMM sessions
    • Weaving in other sessions? Workshop at end of Playground 'use' session?
  • Central Data Service Playground
    • Status reports / Kanban review
    • Documentation site: content, theme
    • 0.1.0 release
    • Knowledge Layer Connector

Minutes:

  • Spring AMM sessions
    • Paul: can make changes to the timings if you need.
    • Discussion of making the end of the morning a working session.
    • AI: Need to calculate the timings. Three playground sessions, then working session.
  • Central Data Service Playground
    • Status reports / Kanban review
      • Steve:
        • WAII VISS Server IoTDB documentation and runtime configuration for connector merged upstream. Will rebase Playground on upstream after spent some time on playground documentation.
        • Working on content for Playground doc site to add baseline why/why/how introduction and getting started. Work taking place on my fork and presented as WIP PR here https://github.com/COVESA/cdsp/pull/27
      • Arnaldo:
        • Continuing work on Realm integration.
    • Documentation site
      • Brief discussion of Hugo themes. Steve seems some limitations in the current Learn theme and has done some experiments with Hextra that adds useful features like Cards and has more normal heading type size scaling. Small example here https://slawr.github.io/cdsp-doc-hextra-trial/docs/
    • Discussion of 0.1.0 release around time of AMM release

13th March 2024

Agenda:

  • Spring AMM sessions
    • Weaving in other sessions?
  • Central Data Service Playground
    • Covesa Board
    • Status reports / Kanban review
    • Continue discussion of Knowledge Layer Connector. One related aspect is the topic of schemas on the data layer side.
    • Roadmap/backlog/work package definition.
      • What does AMM release look like?
      • Feeders
    • Possible online hosting of Playground

Minutes:

  • Sml group: Swen, Steve, Paul, Haonan
  • Central Data Service Playground
    • Steve presented the development status to the Covesa board today
    • Status
      • Steve has sent PR upstream documenting use of Apache IoTDB as WAII Data Store backend. Covers for example runtime assumptions, e.g. schema, that a feeder or client developer would need to know about. Also how to seed the DB.
      • Content will be reusable in Playground.
      • He also rebased the code to add runtime configuration of the IoTDB connector through a config file on current upstream master and sent PR
    • Discussion of Swen's idea for online hosting
    • Discussion of app embedded DB schema
    • Steve summarised what the content of the likely first 0.1.0 release will be and plans for roll out.

6th March 2024

Agenda:

  • Spring AMM sessions
  • Central Data Service Playground
    • Status reports / Kanban review
    • Continue discussion of Knowledge Layer Connector. One related aspect is the topic of schemas on the data layer side.
    • Roadmap/backlog/work package definition.
      • What does AMM release look like?
      • Feeders
    • Possible online hosting of Playground
  • AoB


Minutes:

  • Sml group: Ulf, Swen, Steve
  • Central Data Service Playground
    • Status reports
      • Apache IoTDB
        • Now upstream WAII VISS git rep move is complete Steve will rebase and upstream the config file support.
        • Extending WAII tutorial to document IoTDB connector is almost complete. Will send PR upstream.
    • Knowledge Layer Connector: Haonan has reported that Artifact JSON-RDF Converter outline has been updated.
    • Discussion of the likely content of the pre-AMM release.
    • Discussion of the current thinking for roll-out: get initial documentation in place, roll-out to active Covesa devs, then wider membership/community using blog/e-blast.
    • Swen outlined the benefits and possible method for online hosting of the Playground.
      • Wide ranging discussion of the possibilities: costs, connecting to other systems, scaling, flexibility etc.
      • Interesting idea that needs further discussion.

28th February 2024

Agenda:

  • Spring AMM sessions
  • Central Data Service Playground
    • Status reports
      • Upstreaming Apache IoTDB support into WAII VISS Data Server
      • Apache IoTDB runtime configuration support
      • Online documentation
    • Continue discussion of Knowledge Layer Connector. One related aspect is the topic of schemas on the data layer side.
    • Roadmap/backlog/work package definition. What does AMM release look like?
    • Feeders
  • AoB

Minutes:

  • Central Data Service Playground
    • Status reports
      • Online documentation: Steve has merged Ulf's online documentation PR to add the Hugo setup. Next step is enabling the workflow to automatically build and publish any content.
      • Apache IoTDB state storage: Steve has added runtime configuration (where to find DB, what database path to use etc) support for the WAII IoTDB connector. It's available in his PR https://github.com/COVESA/cdsp/pull/20. He will send a PR upstream to WAII once its moved to its new home.
      • Realm state storage:
        • Arnaldo had questions about how best to handle the paradigm difference between the typically complex documentation schema used in Realm and the key/value pair schema of VISS/WAII. A second challenge is Realm has C++, but no Go client/binding so how best to interface to WAII get/set methods in Go?
        • Discussion about possible approaches:
          • Complex schema
            • Steve: Same problem exists I think for the JSON-schema to RDF connector for the knowledge layer. We've started with simple with key/value pairs in the store for maximum flexibility, but approaches will need to be found for more complex schema as we go along.
            • Swen: I saw this problem when working with Realm cases. We added accessor methods to our solutions to allow interfacing to other systems.
            • Discussion wondering how BMW VISS implementation had addressed the same issue. Arnaldo/Haonan could look for internal suggestions.
          • WAII connector
            • Steve showed the three WAII methods to be supported (init, get, set) which have straight forward parameters.
            • Two ideas suggested:
              • Use Go binding to other languages. Ulf had succesfully used a package that provided type conversions and binding for C.
              • If Realm has IPC support then it could be used form the Go methods. Ulf explains the Redis connector uses a unix socket.
      • Out of time to discuss Knowledge Layer Connector this week.

21st February 2024

Agenda:

  1. Spring AMM sessions
  2. Central Data Service Playground
    1. Status reports
    2. Upstreaming Apache IoTDB support into WAII VISS Data Server
    3. Continue discussion of Knowledge Layer Connector. One related aspect is the topic of schemas on the data layer side.
    4. Online documentation
    5. Roadmap/backlog/work package definition. What does AMM release look like?
    6. Feeders incl WAII, Volvo/Remotive
  3. AoB


Minutes:

  • Spring AMM sessions: Paul would like any updates. Currently abstracts are missing.
  • Central Data Service Playground
    • Status reports
      • Apache IoTDB support
        • Steve created PR #110 in WAII upstream to add the Apache IoTDB support into WAII VISS Data Server. This was merged by the maintainers. Need to add documentation.
        • Steve also created Playground PR #20 to make it available in a WAII fork. Now changes are upstreamed this can be changed to update submodule to the upstream instead.
      • Realm support: No update this week
      • Online documentation
        • Hugo changes were merged but an issue was found in the signoff. Now updated, this will be merged again this week.
    • Knowledge Layer Connector
      • Some background noise on Haonan's end hampered discussion somewhat.
      • Haonan talked about generators to and from SHACL.
      • Work needed to understand how to connect existing tool, which uses web socket as transport and JSON-schema for message, to the VSS State Storage.
      • Some discussion of schemas in state storage. Danger is becoming bog downed in system design discussions of for example VSS tree vs graph. For know the KISS of VSS key/value pairs is beneficial in its flexibility.
    • In coming weeks we need to consider roadmap/backlog/work package definition, in part so we know what we want to say at the AMM.
    • Steve outlined eco-system discussions related to EU Horizon and with Volvo/RemotiveLabs related to feeders.
  • AoB
    • Paul mentions the work on Covesa website related to project descriptions. Data Arch will need to check their entries.

14th February 2024

Agenda:

  1. Spring AMM sessions
  2. Central Data Service Playground
    1. Status
    2. Knowledge layer connector
  3. AoB


Minutes:

  • Central Data Service Playground
    • Status
      • Online doc: AI for Steve to work with Ulf on his Hugo PR remains open
      • Steve has brought the Playground Kanban up to date.
      • Apache IoTDB: Steve has implemented 'set' connector for WAII locally. Code is available in his github fork. Preparing PR to both Playground and WAII.
      • Realm:
        • Steve met with Humza/Arnaldo last Friday to show his integration into WAII
        • Currently Arnaldo considering how best to do the integration. Options include adding Realm as a State Storage backend for all data, e.g. like Redis and IoTDB, or using it in a supporting role where it makes sense, e.g. sync or in Example.
    • Ulf announced he is adding https://memcached.org/ (fast simple key/value pair in-mem store) as an additional State Storage backend to the WAII VISS Data Server.
    • Knowledge layer connector


7th February 2024

Agenda:

  1. Spring AMM sessions
  2. Central Data Service Playground
    1. Based on discussion with Christian Muehlbauer kick off discussion of Connector in the Playground between the data and knowledge layers
    2. Ulf has sent a PR to add the Hugo online doc: Any discussion needed related to that, e.g. workflow, review
    3. Database connectors: status, handling WAII changes
    4. Feeders (time allowing)
  3. AoB

Minutes:

  • Spring AMM sessions: nothing to discuss this time
  • Central Data Service Playground
    • New feature idea: Connector between the data and knowledge layers in the DIKW pyramid
      • Kick off of discussion first discussed in previous weeks.
      • Possibility to use BMW Research WS to RDF Converter (see Christian presentation below). Christian has some personal leave in coming weeks. Haonan will step in.
      • Haonan offers to do technical overview presentation of converter.
      • Steve suggests using the proposed Artifact design methodology (simplified) as a means to working through what such a Connector should achieve for the Playground. No dissentors. Haonan agrees.
      • Way forward:
        • Haonan will do a technical overview presentation in a future meeting. Goal: group better understands the converter. Date TBD once she is ready.
        • Haonan kindly agreed to do a first draft using the design methodology to define what a Playground Connector should be from her perspective (domain expertise). This can then be used as a basis for wider discussion in the group.
        • AI: Track in meetings.
    • Online documentation
      • Ulf has posted PR to add Hugo static website generator. He needs support to add github workflow to automatically build the doc and publish. AI: Steve to work with Ulf on that.
      • Requst to review PR. Will look to merge in next week.
    • Database Connectors
      • Steve has the 'get' connection between WAII and Apache IoTDB done. Preparing to make code public. He expects 'set' to be added this week.
      • Humza reports that the Realm DB C++ process is done. Just need to integrate into WAII. After discussion Steve will meet with Humza/Arnaldo to do a quick return of experience with his integration to accelerate adding Realm.
      • Answer to question of how to manage WAII changes before they are upstreamed becoming more urgent. Steve will likely create WAII fork so they can be managed in the submodule to keep us moving.
    • Feeders
      • Short discussion of feeders

31st January 2024

Agenda:

  1. WAII update
  2. Spring AMM sessions
  3. Central Data Service Playground

Minutes:

  • WAII update
    • Ulf gave an update on WAII improvements related to the new feeder mechanism.
    • Code is merged to master and documentation can be found in the tooling section of the on-line documentation in the tutorial
  • Spring AMM
    • Ulf has added some topics to related to WAII and Commerical vehicles to Paul's Proposal page
    • Arnaldo/Christian have sent a title topic related to touchpoints and the knowledge layer
      • Abstract to be created
      • They say this is possibly less of a readout of existing work and could lead into the discussion of examples and using the Playground
    • Discussion of the third part of the Playground session covering examples and using it and how to incorporate the other sessions
    • Thought needs to be given as to whether to have a formal workshop session in the programme or an informal one with involved members outside the programme
  • Central Data Service Playground
    • Status
      • Steve has done initial integration of IoTDB connector into WAII. Builds and runs. Now need to debug integration issues.
      • Arnaldo continues to work on Realm integration. C++ backend nearing completion. Connecting to WAII after that.
    • Phase 1 PoC
      • What are the big picture things in the backlog?
        • Source license
        • On-line (Hugo) doc PoC
          • Christian: It would be useful to paint the big picture of relationship to other projects. I can perhaps contribute something in that regard
      • Contributor outline
      • Source documenation

24th January 2024

Agenda:

  1. Spring AMM sessions
  2. Central Data Service Playground
  3. AoB
    1. (Ulf): WAII update


Minutes:

  • Spring AMM sessions
    • Steve has added an outline for the three Playground sessions to the planning page.
    • Agreement in meeting to propose those as placeholders in Paul's planning
    • Ulf will add some sessions on his WAII work
  • Playground
    • Decision taken to merge Steve's PR to give the project master branch some structure. This will make it easier for others to parallel work.
    • Status
      • Adding Realm: Arnaldo says he has the C++ process written to act as a Realm instance orchestrator
      • Adding IoTDB: Steve is working on connecting WAII to IoTDB using the IoTDB Golang client.
    • Christian presents his initial thoughts overlaying the work BMW have presented in recent AMMs onto the Playground
      • Christian Proposal.pptx
      • General agreement that additional viewpoints are needed to logical and implementation in presenting the Playground and that shared diagrams are useful.
      • Discussion on what components might be open sourced and could be integrated. RDF converter would be a good candidate to examine for providing a connector between data and knowledge layers.
      • Christian will be taking some time off in coming weeks but is hoping Haonan can substitute as she is very familiar with the RDF converter.
    • Open decision: need to agree how to handle WAII changes. Upstream, fork for git submodule or git subtree for example?
  • AoB
    • Ran out of time. Ulf prefers to defer WAII update to next time.


17th January 2024

Minutes:

  • Discussion of Spring AMM sessions.
    • AMM Commitee wants to make schedule public end of Jan
    • Data Arch planning page here 2024 Spring AMM Planning (Data Architecture and Infrastructure). Feel free to add your ideas there.
    • Steve proposes three linked themes for sessions on the Playground
      • High level intro (why, what)
      • Technical overview (more detailed on how and the code)
      • Focus on using the playground through examples. Akin to the BMW presentations in prior AMMs.
    • General agreement that would be good approach.
  • Central Data Service Playground
    • Steve summarises Friday meeting with Arnaldo and Christian/Haonan. Succesfully worked through Arnaldo's issues with WAII Docker bring up.
    • Arnaldo documented list of gaps in instructions for a clean build.
    • Steve used this to raise additional issues in WAII github with doc or code gaps.

10th January 2024

Agenda:

  • Central Data Service Playground
  • Database abstraction and feeders
  • AoB
    • Ulf has WAII update

...