Page History

...

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

3rd July 2024

Agenda:

• Playground Kanban "stand-up meeting": In-progress task status, major new items
• Docker: Brief summary of my PR above.
• DB Schema generation: I had some discussion with Gunnar in CVI about this. Basically keeping the meta-data for it with VSS as a layer, rather than dislocated in for example a template language config file. I think ultimately I need to write a fuller proposal that can be discussed, but it perhaps warrants a short discussion if people have input to help form the ideas.
• Fall AMM: deadline for talks is end of the month. We need to discuss what we want to do, including the possible extra technical day.
• AoB

Minutes:

• Kanban stand-up meeting:
  • Knowledge Layer Connector, Christian: Started on skeleten PoC DB router in information layer
  • IoTDB Data Processing, Steve: A WIP PR has been added https://github.com/COVESA/cdsp/pull/52 which adds the optional IoTDB Data Quality Library to the Playground IoTDB docker image and configures IoTDB for access from Grafana.
  • uProtocol Simulator: waiting for update from GM
• DB Schema Generation:
  • Discussion of providing a mechanism for DB Schema generation for VSS nodes. This would accelerate users ability to more quickly get started with the Playground as it could automate the generation of all nodes.
  • Steve and Christian think this could be useful. Christian in addition raises a similar use-case for the knowledge layer, e.g. SHACL generation. There was some conversion to SHACL in the past.
  • Idea brainstorming:
    • Rough requirements:
      • Input: VSS vspec (a reduced vspec could be input if only a few nodes are required)
      • Generation:
        • Template language + config (config is the description needed to match VSS to the DB)
      • Output: schema for DB X
        • Example: Series of lines to create schema for each VSS node e.g CREATE timeseries.Vehicle.Speed (datatype=INT, compression=X, encoding=Y, meta-data=Z)
    • Steve: In discussion with Gunnar in CVI it was considered that this mapping meta-data could be held in a VSS layer/overlay (closed to the source) rather than in an isolated stand-along config file. If the existing VSS overlay mechanism did not support it, then evolving VSS overlays to be something closer to IFEX layer mechanism could.
  • VSS layer:
    • vehicle.speed DB meta-data=> data-type=INT, compression=squashy, encoding=super-encoding, meta-data="some attribute"
  • Generation / vss-tools:
    • Christian asks about doing this in vss-tools.
    • vss-tools has good set of meta-model functions now, which means generator largely just needs to contemplate output side so could have:
      • vspec2iotdb
      • vspec2realm
      • vspec2shaql
• Fall AMM
  • COVESA wants technical session proposals by end of the Month.
  • So we need to contemplate:
    • Weds/Thurs Main Conf: Technical Sessions
      • e.g. Outreach etc.
    • Tues Smaller Conf: Workshops
      • e.g. Playground internals
  • Steve will put up the usual page for ideas
  • Paul: COVESA page here All Member Meeting Planning

26th June 2024

Agenda:

• Playground Kanban "stand-up meeting": In-progress task status, major new items
• Docker: I have been working on integrating the IoTDB Data Quality library and Grafana. That raises some questions about configuration of Docker containers and the source for the parts we integrate. That may be worth a discussion to get some feedback. Particularly from the BMW team who may be doing similar work at the moment.
• @Swen Schisler (Endava) mentioned last week wanting to discuss some of his proposal to the CVI group
• AoB

...