Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Today's minutes

Quick links: CVII home page  Tech Stack components

Wednesday 2022-01-26

Related projects walkthrough (every week):

ProjectPerson reportingUpdates
  • Kuksa.VAL
Sebastian (Bosch)  (tick)

Sys arch documentation to clarify use of VISS for reading and writing data (ref previous week's discussion)

https://github.com/eclipse/kuksa.val/blob/master/doc/system-architecture.md

  • W3C VISS specification (v2)


Ulf  (tick)
Ted as backup 

No discussion about spec
(presentation MongoDB instead)
  • VISS server implementation in Go
Ulf (tick)Nothing this week.

Daniel Wilms (BMW) (tick)
(Gunnar, Sebastian as backup)

Removing min/max in standard catalog because they appeared arbitrary.

Added new signal for SAE autonomy level.

Tools versioning , and how it relates to versioning of VSS standard catalog

Recommendation for allowed_values names/strings.  Used in standard catalog (whenever it is possible to define it from scratch, not constrained by system already).

  • VSSo
Daniel W  
Ted  

Switched to W3C reSpec tooling.  New version including signal definitions derived from VSS catalog.  First public working draft hopefully within a week or so.

Discussed W3C workshop (virtual) in early March and/or in-person meeting in combination with COVESA AMM (Leipzig, end of April)

  • VSC & Tools
Gunnar  Narrowing down tech solution to promote Franca IDL + YAML format as core description format.   (Strategy to allow interchange with other technologies of course still in place)
Increase catalog scope with more proposals to gather interest.
  • CCS-components
Ulf  Nothing new
  • AOS
Artem 

  • Android Automotive VSS→ Vehicle Properties
    Code Generator

Maintenance may be taken over by Stefan at TietoEvery
Eclipse Kanto
(proposed.  worth tracking in CVII call?)
(Thomas S) Possibly focus next wednesday?

Minutes

  • Project update (above)
  • AOS update, more comprehensive:
    • AOS code now in GitHub
    • Apache License 
    • Framework to orchestrate containers
    • Several services in different repositories
    • Working on code coverage for CI tests
    • Follow the README documentation
    • Already used on some production projects
    • May lead to standards for orchestration, control, etc.
    • This covers all the software that runs on the embedded systems
    • meta-layers for Yocto
  • Thomas:  Can we get a demo?  To understand the concept better?
  • Artem: If you have a Renesas starter kit or similar.  You can also try it in a VM on desktop.   Yes to demo (in a week or two)
  • Artem: We have our own CNI for plugins, firewall, = networking configuration for containers.  
    ... not using docker.
    ...Using crun currently (previously runc but now crun).  
  • ...Working on introducing standard K8S APIs
  • Artem: Data side, we wish to stay with CVII work and VSS specifically
  • Artem: We have a YAML based description format. Also monitoring any OCI standards that may apply
  • Gunnar: As noted we should set up a time to discuss overlap of the services description format in AOS and VSC.   
    Gunnar/Artem: Agreed joint desire to consider service description ability using a common language, as VSC project intends to achieve.

  • For information: Data Privacy Initiative
    • COVESA is discussing a Data Privacy oriented project (led by member companies in the legal space)
    • Overview of current rules and regulations, legal risks, counteractions.
    • Create an environment of collaboration to discuss these aspects, in general terms.
    • This topic requires a combination of business management, legal, technical, ...
    • Please reach out to your colleagues (including management, legal) to evaluate interest
    • Likely webinar/Q&A discussion in Feb/March + focus in AMM
  • Meeting CCS → tech architecture.
    1. Meeting 1?  – 30 min overview.  30 min any other topics
    2. Meeting 2?  – Technical work?  Is it implementation focus?  Architecture focus?
    Agendas are important
    One slot is shorter?
    Thomas: Workshop planning - 1h not enough. (4h, less frequently)?
  • Ted: Possibly fewer calls instead?

Relevant links:


...

Wednesday 2022-01-19

Related projects walkthrough (every week):

ProjectPerson reportingUpdates
  • Kuksa.VAL
Sebastian (Bosch)  (tick)Upgrade CI infra to GH actions


  • W3C VISS specification (v2)


Ulf  (tick)
Ted as backup 

Feature freeze agreed.  Polishing ongoing.  W3C process steps.
  • VISS server implementation in Go
Ulf (tick)Protobuf used to encode messages (used as efficient binary/compression of the messages, compared to JSON format) over Websocket/MQTT. Might also be on HTTP.
Compared to JSON as a "compression ratio".

Daniel Wilms (BMW) (tick)
(Gunnar, Sebastian as backup)

enum → allowed_values rename.
(another enum concept is still possible/pending)
Signal list - quality improvements.
Documentation updates 
  • VSSo
Daniel W  
Ted  
As discussed, document is complete, going through a release process.
  • VSC & Tools
Gunnar  Biweekly to weekly meetings
Exact time TBD, planning process
  • CCS-components
Ulf  (tick)ovds-client (VISS client) updated to also support protobuf feature.
  • AOS
Artem (error)
next week full update
  • Android Automotive VSS→ Vehicle Properties
    Code Generator

Request for new main developer/maintainer.
Eclipse Kanto
(proposed.  worth tracking in CVII call?)
(Thomas S) Thomas will be an ambassador for this project.  Exact VSS connection not known yet.

Minutes

...


Next week's agenda

Agenda/Minutes:

Minutes

  • Alexander:  BMW publishing code around GraphQL server, mapping VSS to GraphQL, and resolving requests by translating how to get the data from underlying platform (.e.g. through Franca defined interfaces, etc.)
    Also, a demo 

...

ProjectPerson reportingUpdates
  • ioTEA/Vehicle Edge

Mike Haller (Bosch) (error)

Thomas Spreckley (error)



  • Kuksa.VAL
Sebastian (Bosch) (error)
  • VISS server implementation in Go
Ulf (tick)Minor fixes

Daniel Wilms (BMW) (error)
Gunnar   (tick)
(Sebastian as backup)

This week: VSS-layers discussion.  Refer to minutes below.


  • VSSo
Daniel W (error)
Ted 

  • VSC & Tools
Gunnar  (tick)

See presentation from last week's AMM https://at.projects.genivi.org/wiki/display/WIK4/Slide+Decks+and+Videos

  • W3C VISS specification

Ted (question)

Ulf (tick)

Discussions on how to modify specification to better support in-vehicle web apps.  (Access control)
Questions around Service discovery, versioning of VSS (how to know what "interface version" (VSS) you are speaking to)

  • CCS-client repository
Ulf (tick)
  • AOS
Artem (tick)
Completing review towards open source code publication.

Apologies

Minutes

  • Report out from VSS layers discussion
  • Relatively long discussion on VSS versioning (see note on VISS above)
  • Still preparing/approval process for a set of VSS related tool implementations from OEM.
  • Artem:  VSS, VISS, implementation optimizing for edge-computing (different/comprehensive access control mechanism).  Transports. CNI.

...