Page History

[ Permanent link:  Tech stack overview ] 

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

...

Wednesday 2021-08-25

Project	Person reporting	Updates
ioTEA/Vehicle Edge	Thomas Spreckley	Node.js and python for containerized integration tests.  DAPR integration demo Bugfix Seat adjuster demo.  Developed, not pushed public though.
Kuksa.VAL	Sebastian	Merged first gRPC, no docs yet and don't ask... :) First logging feature impl.  Useful for debug/development.
VISS server implementation in Go	Ulf	Working on TLS implementation
VSS & Tools	Daniel Wilms  Gunnar    (Sebastian as backup)	For values that are defined in model (default, or min/max limits), shall "0" be valid if the signal datatype is float, or shall we require it to be "0.0"?  Discussion on  Structured datatypes support?   Major discussion opened, it is a fairly major change if included.  And of course discuss syntax in that case. Extensible (new) datatypes and units, no progress yet. vss-tools:  "vspec2yaml" proposal.  vspec is already yaml, but this expands all instances and flattens into a single output file, and includes uuid values.   Not yet accepted, maybe rename tool since vspec is basically yaml already.
VSSo	Daniel W  Ted	Rudimentary automated mapping VSSo<->DTDL
VSC & Tools	Gunnar	Fix needed to use python 3.8 (currently works only on 3.9) GitHub actions now run unit tests README updates to document gen() function changes
W3C VISS specification	Ted Ulf	Feedback on first public working draft: Minor bug - all messages to provide timestamp uniformly Bandwidth usage due to access token sent with every request.  Discussing if the token could be used like a session, for example by sending only the signature as a reference to a token that had already been authenticated.  Traditional session-cookie possibly going out of style in the future?
CCS-client repository	Ulf	-
AOS	Artem	-

...

• 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

...