Page History

[ Permanent link:  Tech stack overview ] 

Wednesday 2021-09-15

Project	Person reporting	Updates
ioTEA/Vehicle Edge	Thomas Spreckley (Bosch)
Kuksa.VAL	Sebastian (Bosch)
VISS server implementation in Go	Ulf
VSS & Tools	Daniel Wilms (BMW) Gunnar    (Sebastian as backup)	Proposal for dynamic units almost done.  Just a rename remaining.
VSSo	Daniel W Ted
VSC & Tools	Gunnar	Bosch joined this week's meeting.  Early discussion.
W3C VISS specification	Ted  Ulf
CCS-client repository	Ulf	-
AOS	Artem	-

Minutes

• AASIG generation under way
• AVRO serizliation updates

...

Wednesday 2021-09-08

Wiki was down so these minutes were taken offline, and later added:

1. Standard project updates

Kuksa

• Unit tests for gRPC code
• Investigating switching from Jenkins to GitHub actions
• ioT-event-analytics / vehicle-edge
• Working on npm packaging (npmjs organization account now exists)
• Quality checks/
• Suitcase demonstrator including hardware, includes gRPC to communicate with Vehicle
• API. RPi ARM 64 bit.

VSSo

• Refine first version
• A bit more structure to the process
• Discussions continued with Microsoft, conversion to DTDL

VSS

• Continued discussions on units and datatypes

AOS

• Additional discussions with various stakeholders in industry. Want to get the code and
• the container (definition) specification into the open. Registration framework.
• Some inputs drive toward constrained environments. Small efficient implementations
• required for data-servers The full Go-lang VISS server might not fit, k3s and others
• might also not "fit".
• Higher modularity is preferred

VSC

• PR + examples added to master branch in the VSC repository.
• vss-tools (Android)
• A document provided to outline plan, and basic file structure
• Looking for strengthening the implementation team

VISS

• Improvements being done from feedback (pull requests) based on the first public
• working draft

2. Other minutes

• Mike Haller (Bosch) introduces himself. New product owner for IoTEA.
• Artem EPAM might have developers free in 2-3 weeks
• AMM update, reminder to register
  
  

...

Wednesday 2021-09-01

Project	Person reporting	Updates
ioTEA/Vehicle Edge	Thomas Spreckley (Bosch)	Integration test pull-request, renamed test APIs.  More friendly integration in CI pipeline npmjs.org now has a package for ioTEA, with information PyPi will get a package as well Prepare release process, 0.6.0 release is imminent
Kuksa.VAL	Sebastian (Bosch)
VISS server implementation in Go	Ulf
VSS & Tools	Daniel Wilms (BMW)  Gunnar    (Sebastian as backup)	Discussing some new topics related to  possibly new strategy for instantiation of branches ...
VSSo	Daniel W  Ted
VSC & Tools	Gunnar	Magnus F taking some open issues. Inclusions of nested namespaces still to be merged/decided.
W3C VISS specification	Ted  Ulf
CCS-client repository	Ulf	-
AOS	Artem	-

Minutes

• Sebastian and Daniel W, Ulf, sent apologies
• Thomas working on AMM presentation
• eSync Alliance, upcoming
• OPIN, upcoming
• A bit of progress on AVRO encoding.
• (Repeated info), ongoing work on Android VSS-to-Android properties
  • The goal is to create something like this:  aasig-vhal-demo/tree/main/src repository ← this should already compile in AOSP (HAL implementation), but that example has a fixed set of signals.  Instead it shall be possible to code-generation from an arbitrary list of VSS signals
  • Here is a planning/background page named VSS to AOSP translation - WBS
  • The code generator implementation will be a kind of combination of VSS-tools (to read VSS) and vsc-tools (that shows how to use Jinja2 templates for generation).  The tools will need to consume also a "VSS layer" (deployment model) that describes how VSS signals are mapped to their respective Android counterparts. 
    Example of such mapping is on VSS to AOSP translation - WBS

...

• Several vacation/apologies this week from Bosch, BMW, ...
• Project updates above, for those that are available
• Catch up with Artem regarding AOS issues
  • See above
  • Also working on modularity - identifying components for reuse.
• VSC and tools
  • → synergy opportunities with gRPC support in KUKSA.VAL?
  • Let's discuss "decisions" taken during this development → how to find consistency with the VSC-related work (which intends to integrate gRPC and other technologies as needed).
• Awareness:  CVII-TS: Binary encoding for VSS-based data transfer
  • → synergy opportunities with gRPC impl. also here?
  • Artem: We have seen some problems with binary encodings, so JSON mostly for now, which is adequate for a lot of the needs at the moment.  We see potential need (for binary efficient encoding) however.
  • Sebastian:  For gRPC we replace some of the JSON protocol parts of course, but data encoding is often still using strings for simplicity at the moment.
  • Gunnar: OK, I conclude this is still important and interesting to together define one or two canonical binary encodings for VSS.
• Updates/discussion on other priority-list projects:  
  • VISS v2 server Planning / Work Breakdown page
  • Needs a proper "need"/request for resource allocation.  Discussion on if current development frameworks (using python, NodeJS and other) are acceptable in in-vehicle embedded space or if this need actually does  exist already.
• Android AAASIG update
  • Plan to start implementing VSS to AOSP translation - WBS using a combination of VSS-tools examples for reading VSS and VSC-tools examples for code generation using jinja2.  Bittium is  leading.

...

• Introductions (Artem's first meeting)
• Brief discussion on AOS (principles, not the technology).  Embedded parts are planned to be open-source.  Process ongoing (outlook - a few months).
• Artem to give AOS architecture/tech overview next week
• Artem mentioned Android HAL using a VISS-protocol external server was implemented and shown by EPAM a few years ago.  
  • Gunnar:  So this was before AASIG was started...  It is good input, although current work has considered GraphQL as the protocol for the internal VSS-data server.
  • => Artem to provide a link to the published code.
• New table-based tracking of wanted/expected/missing tech stack components was added to the CVII Tech Stack overview page   Feedback/changes welcome!
  • This could drive priority discussions also
• Sub-topics moved to separate pages for deeper analysis, e.g. protobuf (already existed), mqtt (new), etc.
• Eclipse: short discussion on the liaison with Eclipse, to be followed up with the Bosch team

...