Page History

Quick links: [ CVII home page

...

] [ Tech Stack components

...

Related projects walkthrough (every week): SKIPPED

Apologies

• Ulf, Thomas, 

Agenda / Minutes

...

• Andreas Warnke (EB)
• Alan Freedman (Autonomic/Ford)
• Dimitri, SW engineer at Zync

...

]

2022-10-12

Agenda:

1. Project summary
2. Autumn AMM meeting planning + longer term topic planning
3. ISO ExVe update

Minutes:

• WAII VISS based Vehicle to Cloud arch
  • Ulf has pushed the code he had summarised previously that introduces clients to provide a connection between VISS in the vehicle and the cloud.
  • See branch https://github.com/w3c/automotive-viss2/tree/ecuAdaptation for the code. The readme for the vehicle shows the arch
    https://github.com/w3c/automotive-viss2/tree/ecuAdaptation/client/client-1.0/VEC
• Florian continued his standards update from last week:
  • ISO ExVe cont.
    • Florian looped feedback to the ExVe group. The coordinator and Philippe agree that ExVe should be aligned and not creating new data model. Recognition that the two groups move at different speeds.
    • In answer to question whether standard can reference upstream the answer is yes. It would need to specify whether it is informative (info) or normative (must). So ExVe could reference a specific VSS version rather than duplicate.
    • ExVe WG continues to discuss whether its scope is pure data or interfaces as well.
  • Service Orientated Vehicle Diagnostics (SOVD)
    • Florian gave a quick intro to SOVD. This was unfortunately time limited. The group agreed we should ask Florian to expand on the topic after the AMM
    •  Florian's presentation:

      View file
      name Infosharing_CVII_October 2022.pdf height 250

2022-10-05

Agenda:

1. Project summary
2. Autumn AMM meeting planning + longer term topic planning
3. ISO ExVe update

...

• + VSSo breakouts

...

• Primarily working on VISS but it is starting to be complete → new topics come up

...

• Service API definition
  • Improve the description of data-services in the service definition format.
  • Related aspects: resources, device, permissions
    → CVII related sub-tasks that we ought to work on:
  • Better description of which protocols are used
  • ... and the exact interface if it is a RPC protocol (i.e. reference a "VSC interface")
  • ... and a common methodology for permissions definitions.

permissions: 
   vis:
      Attribute.Body.Vehicle.VIN : "r"
      Attribute.Body.Vehicle.VIN : "r"
  

...

• Methods, access control etc

...

Wednesday 2022-01-26

Related projects walkthrough (every week):

ProjectPerson reportingUpdates

• Kuksa.VAL

Sebastian (Bosch)  

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  
Ted as backup 

No discussion about spec
(presentation MongoDB instead)

• VISS server implementation in Go

Ulf Nothing this week.

VSS & Tools	Daniel Wilms (BMW)

(

Gunnar, 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.

Erik J or Sebastian S as backup)

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

Processed PRs. Merged two-wheeler/motorbike profile.
VSSo	Daniel Alvarez (BMW), Felix (Bosch) Ted
VSC & Tools	VSC team members

CCS-components

Ulf

Nothing new

AOS

Artem 

Artem (EPAM)
Android Automotive VSS→ Vehicle Properties Code Generator

Maintenance may be taken over by Stefan at TietoEveryEclipse Kanto
(proposed.  worth tracking in CVII call?)

Covesa GraphQL components	Alexander Domin (BMW)
Eclipse Kanto	(Thomas S)

Possibly focus next wednesday?

Minutes

...

• 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

...

• 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

...

Minutes:

• Florian gave an update on ISO ExVe
  • Liason agreement concluded with Covesa
  • WG 6
    • REST (web) API for external access to car data
  • Discussion of  ExVe thoughts around data models and the challenges of firstly avoiding competing models and secondly the slow speed of ISO updates. If ISO adopts VSS as the model or aspects of it for example there is still a challenge around the version it uses and a probably faster moving VSS version upstream.
  • Discusssion of the use of VSS rule set outside of the VSS standard catalog, e.g. it would be useful for interoperatability, example would be development cost sharing and familarity, if non-VSS standard catalog data used the VSS rule set.

2022-09-28

Agenda:

1. Project summary
2. Autumn AMM meeting planning + longer term topic planning

Minutes:

• ISO ExVe
  • Florian kindly offered to give an update on the state of the data model discussion in ISO ExVe next week
• Discussion of 2022 Autumn AMM Detroit Planning (CVII Tech Stack)
  • VISS client
    
    • Ted reports that where to do VISS client presentation discussed in W3C call. Paul will be discussing with conference team.
    • Ted is owning liasion with Issac and team.

2022-09-21

Agenda:

1. Project summary
2. Autumn AMM meeting planning + longer term topic planning

Relevant links:

• CVII Tech Stack
• Towards CVII pluggable components
• CVII Tech Stack Terminology

Wednesday 2022-01-19

Related projects walkthrough (every week):

...

Kuksa.VAL

Sebastian (Bosch)

Upgrade CI infra to GH actions

W3C VISS specification (v2)	Ulf

 

, Ted as

backup Feature freeze agreed.  Polishing ongoing.  W3C process steps.

backup (both Geotab)
WAII VISS server implementation in Go

Ulf 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".

	Ulf	Working continuing on ECU deployment using WAII. Public updates expected soon.
VSS & Tools	Daniel Wilms (BMW)

(

Gunnar,

Erik J or Sebastian S 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

There is a new PR to document more of the project management in markdown format
VSSo	Daniel Alvarez (BMW), Felix (Bosch) Ted	Gen tooling for VSS v3, one passed, one failed. Following up to fix latter. Meetings have restarted.
VSC & Tools

Gunnar  Biweekly to weekly meetings
Exact time TBD, planning process

VSC team members
CCS-components

Ulf  ovds-client (VISS client) updated to also support protobuf feature.

Ulf
AOS	Artem

next week full update

(EPAM)
Android Automotive VSS→ Vehicle Properties Code Generator

Request for new main developer/maintainer.

Covesa GraphQL components	Alexander Domin (BMW)
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

• CVII Tech Stack
• Towards CVII pluggable components
• CVII Tech Stack Terminology

Wednesday 2021-12-22

Minutes:

• Short readout on Autosar discussions
• Steve outlined the current plan for the AMM / future planning workshop (2022 Autumn AMM Detroit Planning (CVII Tech Stack)
  • • Please add any topics you wish to discuss

2022-09-07

Agenda:

1. Project summary
2. Autumn AMM meeting planning + longer term topic planning
3. Rescheduling VISSv2 client deep dive

...

Kuksa.VAL

Sebastian (Bosch)

W3C VISS specification (v2)	Ulf

 

, Ted as

backup All open questions have been resolved (for the moment

backup (both Geotab)
WAII VISS server implementation in Go

Ulf

Ulf
VSS & Tools	Daniel Wilms (BMW)

(

Gunnar,

Erik J or Sebastian S as backup)

Meeting series postponed until January

(See previous week)

	See vss and vss-tools github for updated PRs and issues. Marketing announced v3 release.
VSSo	Daniel

W  
Ted  

Alvarez (BMW), Felix (Bosch) Ted

Meetings restart in two weeks

VSC & Tools

Gunnar  

VSC team members

Consolidation work on tooling continues

Meeting series postponed until January

CCS-components	Ulf

-- 

AOS	Artem

Publishing has started on GitHub, and is still ongoing

(EPAM)	No announcements. See source repository for code changes
Android Automotive VSS→ Vehicle Properties Code Generator

"Simple compile check" in CI system (stubbed out dependencies).
See GitHub actions, currently on this branch here for example.

	Calls restarted weekly. Tues at 5pm CET. Shared status with Conjure. Discussion about VHAL conversion.
Covesa GraphQL components	Alexander Domin (BMW)

Updated to generate all type=conversion functions on the fly. 
Track Manu's vss-tools fork / PR for status.

Eclipse Kanto	(

proposed.  worth tracking in CVII call?)not discussed today

Apologies

Ulf Bjorkengren 

Agenda/Minutes: 

• Project updates, see above.
• BMW / GraphQL – end 2 end demo
  • https://github.com/COVESA/graphql-vss-data-server is the latest repo (see also related ones).
  • Still to come:  Code generator from GraphQL schema itself.  Classes (stubs) that are implemented by the developers to make the binding connections.
  • The demonstration and part of the discussion was recorded for future use (link pending)
•  Reminder to review Towards CVII pluggable components, and CVII Tech Stack Terminology to give feedback
• Also the CVII Tech Stack components area (presented last week)

Wednesday 2021-12-08

Minutes:

• AMM / future planning (2022 Autumn AMM Detroit Planning (CVII Tech Stack)
  • Next steps
    • Discuss data storage proposals with Adnan to get clearer picture of what and when. Can we clarifty before AMM or do we workshop it at AMM for example
    • Schedule needs some time (1hr at least?) to allow for the future planning discussion whilst we are together
    • Go back to Issac to discuss where to schedule VISSv2 client outreach. If there is an AMM session it will feed into the schedule
• VISSv2 client from UMA
  • Deep Dive possible but summer slowdown may result in low attendance. What is best?
  • Ted: AMM session if remote allowed? 30 mins?
  • Paul/Steve: possible
  • Client has a focus on security so there is a connection to the security

2022-08-31

Agenda:

1. Project summary
2. Autumn AMM meeting planning + longer term topic planning

ProjectPerson reportingUpdates

Kuksa.VAL

Sebastian (Bosch)

Released last month's recent changes into a tagged version.  See changelog.  

https://github.com/eclipse/kuksa.val/releases/tag/0.2.0

W3C VISS specification (v2)	Ulf

, Ted as backup

• Discuss optional features

• Decision around the API to query feature-capability of the VISS server.

Very few open questions at the moment, so it seems like the specification is starting to be considered "complete", thus starting planning for formal proposal

• VISS server implementation in Go

Ulf Protobuf trials are coming for the payloads (next year)

• VSS & Tools

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

Enum functionality discussion

• Does the current function suffice?
• Discussion about extended feature/capability of assigning fixed values, etc.

• VSSo

Daniel W  
Ted  

Documentation up to date.
https://w3c.github.io/vsso/
Publishing plans in January.
Workshops being planned, February.

• VSC & Tools

Gunnar  

meeting delayed

• CCS-components

Ulf  -- 

• AOS

Artem
no news today, awaiting open-source releaseEclipse Kanto (tbd)IoT/edge cloud connector piece
(to be determined the association to data-model/services-model)

Apologies

Agenda/Minutes: 

• Sebastian: GitHub Packages are recommended, for container images for example.
• Stephen:  Common implementations?  E.g. AOS has VISS server, KUKSA.val has VISS server, etc.  Upgrades to latest protocol version - shared implementation?
• Alexander: Additional code is coming from BMW (ref: last week's walkthrough).  The implementation of the actual GraphQL server is coming next.
• Further discussion on how to organize joint development projects:
• Provide feedback to component names in: CVII Tech Stack Terminology - temporarily stored on GENIVI Wiki:
  • https://at.projects.genivi.org/wiki/pages/viewpage.action?spaceKey=MIG&title=CVII+Tech+Stack+Terminology
• Also read (again) Towards CVII pluggable components and consider if these are obstacles to collaboration, and which ones we can overcome.

Wednesday 2021-12-01

Minutes:

• AMM / future planning
  • Planning page added 2022 Autumn AMM Detroit Planning (CVII Tech Stack) and populated from in meeting discussion. Feel free to add ideas
• Discussion of Android EG / VHAL

2022-08-24

Agenda:

1. Project summary
2. Autumn AMM meeting planning + longer term topic planning
3. Brief report on production system using Kafka and MQTT between vehicle and cloud

...

Kuksa.VAL	Sebastian (Bosch)	- -
VISS server implementation in Go	Ulf	–
VSS & Tools	Daniel Wilms (BMW) (Gunnar, Sebastian as backup)	v 2.2 tagged (1 week ago) Review update proposals in VSS standard catalog on several points (open for review another week) Redefining enum was further discussed
VSSo	Daniel W   Ted	Draft spec proposal for reading
VSC & Tools	Gunnar	referring to last week's updates
kuksa.val databroker simple integration/API tests https://github.com/eclipse/kuksa.val/pull/330  -  Ship VSS 3.0 and make it loaded by default in kuksa.val server container https://github.com/eclipse/kuksa.val/pull/331   - Load VSS3.0 as default in kuksa.val databroker container https://github.com/eclipse/kuksa.val/pull/332   - minor documentation fix for DBC feeder https://github.com/eclipse/kuksa.val.feeders/pull/16
W3C VISS specification (v2)	Ulf, Ted as backup (both Geotab)	Call for review for next step of standard process for v2 being prepared. BMW report source release for their implementation being prepared. See here https://www.w3.org/auto/wg/wiki/VISS_implementations
WAII VISS server implementation in Go	Ulf	New features coming in coming weeks related to in-vehicle client. Related to arch Ulf previously outlined in his vehicle to cloud proposal.
VSS & Tools	Daniel Wilms (BMW) (Erik J or Sebastian S as backup)	See vss and vss-tools github for updated PRs and issues. Discussion of the driver monitoring leaves in driver.vspec. Input requested from people in this field.
VSSo	Daniel Alvarez (BMW), Felix (Bosch) Ted	First public working draft of standard as 1st standardisation milestone. Ted will be testing the tooling.
VSC & Tools	VSC team members	Discussion of MBition consolidation work on tooling	W3C VISS specification	Ted Ulf	VSSo was discussed on the WG meeting Simpler authentication flow, change was accepted.
CCS-components	Ulf	–
AOS	Artem	Still working on logistics of publishing open source

Apologies

• Ulf

Agenda/Minutes: 

• Project updates
• Demonstration of end-2-end SOME/IP signal source / GraphQL VSS server (Alexander Domin, BMW)
  • Walkthrough of existing repos, reasons and intentions behind.
  • Live demo
    • Create GraphQL schema with tool
    • Only a single Query / entry point that is matched against the whole Vehicle Tree.  GraphQL schemas can define multiple, but this is how it is done here.
    • Subscription queries are supported
    • Query can include all values of any (sub)type in the tree, or only some, it is very flexible.

Wednesday 2021-11-17

...

• ioTEA/Vehicle Edge

...

Mike Haller (Bosch) 

Thomas Spreckley  

...

CES demo

Minutes:

• Project Summary
  • Android VHAL
    • Chris Tingley from Conjure says they intend to work on VSS to VHAL translation in the autumn. Introduced Chris to Stefan Wysocki the Android EG lead so they can collaborate.
• AMM
  • Need to plan Data Architecture / Infrastructure sessions
    • Ideation on future EG: cloud, in-vehicle
    • Data Storage / sync
    • vehicle to cloud link
    • CCS
• Return of Experience
  • Steve summarised use of MQTT (transport) and Kafka (ingest) outlined in webinar he attended
    • Bringing hyper-connectivity to hypercars with MQTT and Kafka - Mobex

2022-08-17

Agenda:

1. Project Status and info sharing
2. AMM
3. Data Expert Group
4. AoB

Minutes:

• Project Status:
  • VSS v3 released
  • Kuksa.val
    - kuksa.val and kuksa.val.feeders repo completely Apache-2.0 now
    - Removed experimental HTTP interface https://github.com/eclipse/kuksa.val/pull/316
    - Updated all kuksa.databroker dependencies https://github.com/eclipse/kuksa.val/pull/321/files (due to cirtical security bug in nix dependency)
      -  Update architecure pictures (mention GRPC in addition to VISS and add VSS Logo): https://github.com/eclipse/kuksa.val/pull/324 
     - Fix some remaining GENIVI references to COVESA. Better late than never :) https://github.com/eclipse/kuksa.val/pull/327
  • VSS
    - Released Version 3.0 !!! https://github.com/COVESA/vehicle_signal_specification/releases/tag/v3.0 
    - Decided way forward wrt complex datatypes/structs  https://github.com/COVESA/vehicle_signal_specification/issues/326 
    - Updated docs and logo https://github.com/COVESA/vehicle_signal_specification/pull/470 
    - tools: Fixed regression in DDS and GraphQL exporters: fixed issue w.r.t. value attribute generation in DDS-IDL file,  Extend exporter tests
• AMM
  • Paul: call for session topics.
  • Steve: To help plan whether we can have workshops who plans to travel? Seb hopes too, Ted yes, Ulf not clear yet, Steve yes.
• Data Expert Group
  • Approved in board meeting.
  • Now move to implementation.
  • Call for chair and co-chairs/project leads

2022-08-03

Agenda:

1. Project Status and info sharing
2. AoB

Minutes:

• With only four present with the summer slowdown and other absences had a general state of the nation discussion including the EV meeting directly prior to this one.
• Ted reported from the W3C call that BMW continue to work towards publishing the source to their VISS server

2022-07-27

Agenda:

1. Project Status and info sharing
2. AoB
   
   1. Data EG

Minutes:

• Discussion of proposed Data Expert Group
• VSS
  • Discussion of complex data types in VSS
  • Nik: Is VSS v3 coming soon?
  • Seb: Should be soon after summer break

2022-07-20

Agenda:

1. Project Status and info sharing
2. AoB
   
   1. Board discussions

Minutes:

• Ulf: Should we discuss the EG changes discussed in the recent board meeting?
  • Paul summarises the current situation

2022-07-06

Agenda:

1. Project Status and info sharing
2. AoB
   
   1. Meeting next week

Minutes:

• Kuksa
  • Seb outlines background to the work in progress changes listed above
  • gRPC
    
    • Steve: You mentioned gRPC vs VISS. Where there use cases where you favoured one over the other that necessitated the new work on gRPC?
    • Seb: gRPC came about from feeders where gRPC more easily connected to lang like C++ then having to use websocket for VISS.
    • Steve: Ted reported last week that there were already multiple definitions for binary VSS data serialisation in protobuf. Is this adding another? Coordination needed?
    • Seb: Good point. Currently only single values are supported so there is no much (no data stream) to serialise.
  • kuksa dataserver:
    • gRPC get/set VSS data server. No WS
    • Currently parallel to kuksa VISS server.
    • Internal discussions ongoing in Bosch about respective uses for each and to what extent they may merge.
• AoB
  • Steve will be travelling after the Covesa Board Meeting at the time of next weeks call. Do you want to have a call next week or skip?
  • Paul B will host the call.

2022-06-29

Agenda:

1. Project Status
2. Continue Vehicle Edge To Cloud Edge (VE2CE) project proposal (Slides here) discussion from last week

Minutes:

• Misc info sharing

  • Ted: there are 3 VSS protobuf serialisation versions - work ongoing to converge:

    1. WAII
    2. AWS Fleetwise
    3. vss-tool contrib
  • Ted: Eclipse sdv contributor reveal tomorrow. Expected that some will be building on CVII/VSS
    • https://sdv.eclipse.org/sdv-contribution-day-june-2022/
  • Steve: repeat of Ford EV project proposal kickoff planned for Asia friendly timeframe
• Vehicle Edge To Cloud Edge (VE2CE) project proposal
  • Nick: It would be good if the proposal addressed the relationship to existing standards e.g. ExVe, SOVD so its clear avoidance of fragmentation is preferred.
    
    • Service Orientated Vehicle Diagnostics (SOVD)
      • They are working with AUTOSAR Concept 704
• Ted: EU interest in VSS https://ec.europa.eu/eusurvey/files/228a780b-d76e-4b63-bc3a-09a292d860ff/a9d67e78-cca0-4076-8d93-93a286654101

2022-06-22

Agenda:

1. Project Status
2. Continue project proposal (Slides here) discussion from last week

Minutes:

• Coordination
  • Paul: Ford proposal meeting tomorrow.
  • Steve: Plan to repeat this in an asian friendly timeslot
  • Paul: Digital.auto proposal. VSS playground. Connection to academic work. Possibly 13th July.
• Vehicle Edge To Cloud Edge (VE2CE) project proposal
  • Ulf has updated proposal document.
    • Added backend client: to control what is sent from server, also allow writing to server from cloud.
    • See added slides for change log.
  • Discussion of Nick's point about how the proposed APIs relate to ongoing standards work, e.g. ExVe and ISO
    • Point made about ongoing work by Covesa to maintain outreach to such organisations.
    • Detail is multi-faceted: transport / messaging / data pipes (possibly proprietary), data models
    • ISO currently does not specifiy data model but plans to look at what is available including VSS
    • Florian: ISO API currently most closely fits CIAPI
  • Ulf outlines how VDAPI can also be used as a App data API (see news slides in his proposal) as well as for data feeder
    • Steve: Are requirements for southbound interface to car network such as Some-IP/CAN/LIN quite different from an end user app, or to lesser extent in-vehicle "function app"?
  • Next steps
    • Paul: need to figure out how to bring this to a bigger audience to grow interest.
    • Ulf: lets discuss next week

2022-06-15

Agenda:

1. Project Status (brief)
2. Vehicle Edge To Cloud Edge (VE2CE) project proposal

Minutes:

• Brief project review
  • Paul: If anyone wants invite to the discussion of the EV Charging proposal from Ford please ask. 
• Vehicle Edge To Cloud Edge (VE2CE) project proposal
  • Ulf presented proposal for CCS follow on. Slides here
  • Session recorded. Will be added once wiki page for proposal added.
  • Paul and Ulf will work on preparing next step.

2022-06-08

Agenda:

1. Project Status

Minutes:

• VISS web client
  • Ulf outlines features:
    • GUI compared to mix of simple CLI tooling in WAII. Easier to use
    • Supports both "short" and "long term" authentication. Long term support requires changes in WAII
      • Steve: Are the WAII changes being upstreamed and do you see any issues with review?
      • Ulf: Yes should be smooth integration
  • Discussion of possible deep-dive on it
• Vehicle Edge To Cloud Edge - VE2CE
  • Ulf wants to present a proposal next week for a follow on project to CCS.
  • No discussion of the details. Ulf prefers to leave it to the presentation.
  • He will provide a couple of lines for Steve to use in an announcement.

2022-06-01

Agenda:

1. Project Status

Minutes:

• Paul
  • Meeting upcoming to discuss proposal from Ford about collaboration on connecting EV Charging to VSS. Background is open smart use of charging data.
  • Next week he will be at Telematics Detroit. May not attend all meetings. Expect other members to be there also.
• Ted
  • Issac Agudo Ruiz (W3C VISS editor) has created VISS Client he will be open sourcing. He will present in W3C WG but it would be good to repeat in Covesa as well to get word out.
• Seb brings up question of ppl being spread out across multiple meetings
  • Ulf we could do coordination bi-weekly
  • Ted we could alternate: coordination one week, deep dive next week.

2022-05-25

Agenda:

1. Project Status
2. CCS State Storage Deep Dive wrap up

Minutes:

• CCS State Storage Deep Dive wrap up
  • Was useful meeting to update ppl on State Storage component (what it is and its status) and discuss how it interacts with other components
  • Discussion of the slides. Using 'feeders' vs VISS Client to update the VISS Server values. Architecture discussions.

2022-05-18

Agenda:

1. Project Status
2. Next Deep Dive - CCS Component

Apologies:

• Sebastian

Minutes:

• NDN
  • Ted: Tier 1 experimenting. Interesting for its connection to VSS.
• VSSo
  • Ted: Observers welcome to join calls at any time. Observers need to avoid involving in voting or concept introduction. Contributions can also be made through github. Same applies to VISS calls.
• Paul: describing CVII and CVII Tech Stack to various companies. If ppl have input on how best to describe it then please say.
  • Florian: OEM presentation from Graham at AMM. Seen those slides repeated elsewhere since then. May be helpful in terms of where VSS is applicable.
• Next Deep Dive - CCS Component
  • Monday 23rd at 4pm CET.
• Christian: Does it make sense to present/introduce digital.auto (https://digitalauto.netlify.app/) here?
  • Paul, Steve: Yes. Should discuss about what you wish to achieve.
  • Christian: Need to tie technical work to biz connection.
  • Paul: (running out of time) Can take that offline.

2022-05-11

Agenda:

1. Project Status
2. Next Deep Dive - CCS Component

Minutes:

• CCS Components: State Storage Deep Dive Agenda
  • Timing
    • 15-20 min: Ulf Intro presentation on CSS Components: State Storage.
    • 40 min: reaction and building future plan
  • Technical API discussion
    • Design Issues in UIf's presentation
    • Review current State Storage component API
      
      • Anything to fix or extend?
      • In VSS Terminology State Storage is 'simple'. Is this component left (fit) for that use case and something else is needed for 'more powerful' or do we reuse/extend?
    • Abstraction APIs
      • To Feeder, to Server
      • Requirements
        • Speed
          • Low vs medium vs high frequency
          • Native for high frequency?
      • Kuksa.val is also a target
    • Last value vs time series
      • VISS protocol has some TS query
        • 'History filtering'
        • Simple support for this in current WAII. Other process (e.g. comms) must tell WAII to start/stop recordering. Then VISS client (e.g. cloud) must detect vehicle became disconnected and query for missing data.
        • Kuksa currently has no TS
  • Date
    • Monday 23rd May 4pm CET.

2022-05-04

Minutes:

• AMM feedback
  • Paul
    • Workshop
      • Input from Ricardo/NNG on interfacing VSS to ROS RTOS and its DDS messaging
        • Reached out waiting for reply to advance discussion
      • BMW (Adnan) input about links to big tech company
        
        • As above meeting needed to scope out
    • Next AMM
      • Need input on what ppl want to do to make workshops flow more organically
  • Sebastian
    • Workshops
      • Ppl came expecting 'readout' rather than workshop.
      • Positive was the good attendance and many newcomers, but the flipside of that was it was less 'workshopping'
  • Christian
    • Good discussions
    • Mixed expectations of new members/visitors vs call regulars
    • Good attendance in workshops despite them being scheduled at the end
    • It was cool
  • Florian
    • Good balance between panels, biz/tech track and workshops
  • Ted
    • Attended virtually
    • Enjoyed BMW presentation on VISS integration
• CVII Tech Stack Workshop talking points
  
  • SomeIP work occuring in Autosar. No schedule but something to follow.
  • BMW Android/VISS presentation. Major: VISS + Android VHAL feeder, Minor: GraphQL backend.
    • See deep dive discussion below
  • ROS / ADAS DDS to VSS
    • See Paul comment above
  • VSS Feeders / Data Store
    
    • Seb update on kuksa.val CAN
      • Loosely coupled, i.e. easily reusable
      • CAN feeder in python. Nice for prototype but for production likely look C++, Rust
      • CANOPI
      • Next step: wider discussion about reusing this work in eco-system. More eyes on the code etc.
    • VSS Feeder and Data Store abstraction
      • CCS Component status as starting point
        
        • Ulf's CCS component slides as possible starting point to deep dive
      • Need to discuss to what extent abstraction is possible or makes sense and for which use cases.
        • e.g. CCS Component current abstraction is simple single key/value API. Fine for low volume but would not scale.
        • In some cases might make sense to just use highest speed native API
    • Steve suggests start planning Deep Dive to discuss VSS Feeders and Data Stores
      • 1st might be:
        • 20-30 min Ulf present CCS slides, followed by wider discussion about abstraction.
      • Ulf sent apologies today. Steve will discuss with him either next week or slack
  • Deep dive next
    • Steve: What other things do you want to discuss in coming weeks?
    • Seb: Dig into what BMW needed/took from VISS protocol to understand their needs. Input may be useful towards VISS v3.
    • Ted has been having OSS roadmap discussion with BMW. Idea is to schedule meeting with Adnan about above when code available.
    • If meeting is in W3C slot then Ted will arrange 'visitor pass' for CVII members to attend.

2022-04-20

Agenda:

1. Project Status
2. AMM Sessions

Minutes:

• AMM workshop Thursday afternoon: 2-3 hours (Updated working list from last week) 
  
  • Discussion of what the group wants to work on and discuss in near-term
  • Currently the sessions are split into the two related topics VSS Data Storage, including feeders and VSS Data Servers
  • Topic brainstorming:
    • VSS Data Storage (including VSS Data Feeders) (Southbound)
      • Data Storage implementations:
        • DBs: redis, timeseries etc
      • Architecture: Single central vs distributed vs direct sensor connect (bypass store)
      • Feeders: CAN (kuksa.val have closed some gaps), some/ip,
      • Timeseries vs last/single value
      • Interfacing into data servers
    • VSS Data Servers (Northbound)
      • VISS v3? (Duplicate: Will be brought up in prior VISS session so likely handled there)
      • Are VISS backend abstractions possible: storage, feeders?
      • GraphQL - in-vehicle?
        • BMW VISS→Android abstraction/interface/data server
      • VSS Data Servers to cloud
      • Data processing
        • Ted explains they see issues with OEM cloud data. Time slice not short enough for some forms of h/w maintenance wear tracking so have to do their own. Possible need for some in-vehicle processing. Also issues with in-vehicle caching with insufficent IO.
          
          • In-vehicle vs cloud
          • In-memory vs storage

2022-04-13

Agenda:

1. Project Status
2. AMM Sessions

Minutes:

• Project status roundup abbreviated to allow more AMM prep. Any
  
  • VISS
    • Ted: BMW hope to OSS the VISS→Android adapter they will discuss at the VISS session at the AMM by June
    • Ulf is refactoring WAII so the architecture has a much lower number of standalone processes. Work should be complete in 2-3 weeks.
  • Kanto
    • Steve: Tom could you chase Tina for the Kanto presentation please.
  • Aos
    • Steve reports that the public documentation for Aos is now online https://docs.aoscloud.io
    • Work is starting on the previously reported goal of replacing the current VISS v1 server with an OSS replacement to adopt and extend. WAII and Kuksa.val in focus.
    • Work is also starting on some of the VSS related topics mentioned in Artem's presentation last year such as user service migration between cars.
• AMM workshop Thursday afternoon: 2-3 hours
  • Discussion of what the group wants to work on and discuss in near-term
  • Currently the sessions are split into the two related topics VSS Data Storage, including feeders and VSS Data Servers
  • Topic brainstorming:
    • VSS Data Storage (including VSS Data Feeders) (Southbound)
      • Data Storage implementations:
        • DBs: redis, timeseries etc
      • Architecture: Single central vs distributed vs direct sensor connect (bypass store)
      • Feeders: CAN (kuksa.val have closed some gaps), some/ip,
      • Timeseries vs last/single value
      • Interfacing into data servers
    • VSS Data Servers (Northbound)
      • VISS v3? (Duplicate: Will be brought up in prior VISS session so likely handled there)
      • Are VISS backend abstractions possible: storage, feeders?
      • GraphQL - in-vehicle?
        • BMW VISS→Android abstraction/interface/data server
      • VSS Data Servers to cloud
      • Data processing
        • Ted explains they see issues with OEM cloud data. Time slice not short enough for some forms of h/w maintenance wear tracking so have to do their own. Possible need for some in-vehicle processing. Also issues with in-vehicle caching with insufficent IO.
          
          • In-vehicle vs cloud
          • In-memory vs storage

2022-04-06

Agenda:

1. Project Status
2. AMM Sessions

2022-03-31

Agenda:

1. Meeting arrangements for next week - Steve on holiday
2. Regular project recap
3. Develop the deep dive page: What (detail)? When (priority)?
4. AMM 5 min overview session - what to list?
5. AMM workshops - topics

Related projects walk-through (every week):

• Minutes:

  • AMM overview
    • What
    • Achivements
      • GraphQL contributions?
      • WAII: Redis
      • Coordination:
      • Feeder/Storage: Redis, Apache IoTDB, Feeder news
    • Join: meetings and AMM session

2022-03-28 Eclipse Kanto Deep Dive

Agenda:

1. Bosch introduce Eclipse Kanto. It's relation to CVII Tech Stack and VSS eco-system and suggestions for possible collaboration.
2. Discussion

Presentation:

20220315-Eclipse Kanto_covesa_pitch.pptx

Minutes (summarised after the event):

• Konstantina Gramatova introduced Kanto.
• Live demo (see ppt for details)
  
  • Bosch IoT Suite (serverside) providing container image to Kanto.
  • Image contains Kuksa.val as VISS data server.
  • Kanto used to orchestrate running image.
  • GPS used to provide input to data feeder into kuksa.val which was read out to web.
• Recap of some known possible points for container orchestration collab around details missing in current OCI specs for auto needs.
• Kanto team interested in community collab. Team encouraged to feed in the gaps they see.

2022-03-23

Agenda:

1. Regular project recap
2. Meeting time for next two weeks before Europe switches to daylight saving
3. Develop the deep dive page: What (detail)? When (priority)?
4. AMM workshops

Related projects walk-through (every week):

• Minutes:

  • eco-system
    • Ted: Discussion planned with CCC (BMW representative) regarding coordination. They have traction around their digital key (keyless entry) and there are possible connections to VSC, VSS.
  • Eclipse Kanto
    • Thomas wants to go for next Monday 28th at the 'old CCS meeting' time for presentation.
    • Show of hands showed some ppl were available and Thomas wants to go ahead.
    • Rough plan for meeting is approximately 30 mins on Kanto from developers, followed by 30 mins on discussion. Focus is on the business of CVII Tech Stack and VSS eco-system, i.e. shared collaboration on non-differentiating technology.
  • VSS Data Storage
    • Discussion of attaching timeseries DB to CCS statestorage to provide "last value" backend for VISS.
    • Obvious first step. Does not preclude other processes from directly accessing timeseries data.
    • Wider discussion of how timeseries can be helpful, e.g. query and data processing, can follow on.
  • AMM
    • Discussion of CVII Tech Stack and issues around co-existing with parallel VSS track.
      • e.g. VSS has a VSS Layers discussion planned many will want to attend.
    • Deep dive
      • UIf reminds we should not neglect CSS/Northbound to Cloud. Although we need participation from ppl in that area.
    • CVII Tech Stack workshop
      • Seb: I am less interested in architecture discussion.
      • Ulf, Seb and Steve all express interest in discussion on feeders, data storage and data servers.
      • Working idea is for that to be the focus for a workshop. Possibly in afternoon to allow VSS workshop attendance.
      • More detailed discussion points need to be developed ahead of time.

2022-03-16

Agenda:

1. Regular project recap
2. Meeting time for next two weeks before Europe switches to daylight saving
3. Develop the deep dive page: What (detail)? When (priority)?
4. AMM workshops

Related projects walk-through (every week):

• Apologies:
  • Sebastian

• Minutes:

  • Deep dive
    • VSS and VSC cohabitation
      • Tom would like to see the VSS and VSC cohabitation discussion get going before the AMM.
      • Ulf sees a topic connection to VISS.
      • Steve doesn't feel ownership for the topic in tech stack. Clearly it strongly connects to VSC and VSS.
      • Discussion about kick starting. Decision to bring it up in Monday's VSC call, then depending on that possibly take it onto Tuesdays VSS call.

2022-03-09

Agenda:

• Regular project recap
• Decide on timing for extra meetings.
  • Fill out the timing doodle if you have not already.
• Deep dive/AMM topic planning
  • Develop the deep dive page. What (detail)? When (priority)?
  • We need also to work on the topics for the AMM workshops.
  • Deep dive is an obvious input into that. Currently we have 1 hour scheduled. Is that enough?

Related projects walk-through (every week):

• Minutes:

  • Project Summary
    • Kanto
      • Tom reports that Maintainers can do a presentation from March 28th.
      • Discussion of content. Focus of deep dives is the scope of CVII Tech Stack, e.g. shared collab areas and understanding big architecture picture of how components fit together. Suggestion that 50% of time be presentation, 50% discussion of raised collab points.
• Deep dive scheduling
  • Doodle results
    • 5pm CET has good support but clashes with bi-weekly HV call. Paul would prefer to avoid rescheduling it.
    • 4pm CET (old CCS time) slightly worse in support terms. Sebastian may not be able to attend some but says group should go ahead. Ted thinks he can reschedule clashing meeting.
  • Conclusion:
    • Try 4pm CET.
• Deep dive topics
  • VSS / VSC integration
    • Seb: this overlaps with VSS and VSC groups and each has different participants. Needs coordination.
    • Steve: agree. I don't think "where" is important, i.e. not "owned" by Tech Stack, what is important is the topic.
    • Group participants are going to need to coordinate the topic. Upcoming AMM is going to be a good moment for everyone to be together.
    • Who is going to AMM?
      • Seb, Tom, Paul, Steve, Ulf, Florian (maybe), Nick (maybe), Erik, Philippe, Ted (would like to but obviously trans-atlantic)
  • General
    • Steve: please add your thoughts and topics to the deep dive page. Other the coming weeks we should refine and then prioritise to actually start the meetings.
• AMM
  • Steve: Is one hour enough?
  • Agreement that two hours would be better for workshop. Is that possible?
  • Paul will discuss with schedule planners.

2022-02-03

Agenda:

• Regular project recap
• Continue the extra meeting discussions. Work on the "deep dive" topic list.k
  • Fill out the timing doodle if you have not already.
  • Add to the deep dive page.
• AMM topic planning
• Tech discussion with remaining time.

Related projects walk-through (every week):

Apologies:

• Ulf

Minutes:

• Kanto
  • Thomas reports that project leads in Bosch working on Eclipse Kanto would like to present project
  • Source now available on Eclipse github
  • When?
    • Discussion about how to do 30+min session as this meeting has limited time
    • One approach is to do it as a "deep dive". Paul concerned about having people new to CVII having to sit through rest of the meeting.
    • AI: Thomas will get devs to add it as a topic to deep dive page and get feedback on when.
    • 5pm CET Monday is most liked time slot in Paul's deep dive doodle. Paul realises now that clashes with HV bi-weekly.
    • AI: Paul will consider timings.
  • What, why?
    • Assumption is that presentation is focused on CVII Tech Stack goals. Understanding architecture components and non-differentiating areas of collaboration.
    • From initial presentation discussion we can determine collab areas.
      • Some points that came up in first discussion:
        • Service definition
        • Container orchestration configuration
• Extra meeting / deep dive
  • Doodle results show preference for "old CCS time" of Monday 5pm CET.
  • Please update the "deep dive" topics page with your thoughts and ideas. This page will be used as driving force for organisation of coming meetings.
• AMM planning
  • Little time left to discuss. Please think about topic list.

2022-02-23

agenda:

• project recap
• extra meeting discussion
  • CVII Tech Stack: "Deep-dive" topics
• dev org
  • recording task list
• AMM prep
• AoB

Related projects walkthrough (every week):

Minutes:

• Project sync
  • CCS
    • Ulf summarises architecture. CCS State Storage as it is the component in WAII architecture that administrates the WAII VSS Data Store. Implementation allows a plugin approach to data backends. Once done will interface updated component into WAII.
    • Ulf happy to have seperate meeting to discuss details.
    • Sebastian mentions that dapr has a state-storage API to abstract DB backends State management overview | Dapr Docs
    • Work related to what steve is wanting to do with VSS Data Storage in vss-otaku.
    • Having three DBs should give good scope to discussions about VSS Data Stores and their interfacing.
  • Kanto
    • No updates since this project was first added. Should we keep it in the table?
    • Gunnar: We should list projects that have VSS functionality else we could list all dev tools.
    • Sebastian: No public source yet.
    • Proposal to remove it from table for now. We can add it back when needed. Any dissenters? None.
  • AWS
    • Gunnar reports that AWS mentioned they may have some VSS tooling to contribute
• Extra meeting / deep dive
  • Steve introduces CVII Tech Stack: "Deep-dive" topics page. Please add comments and topics.
  • Plenty of topics to get us started. Missing piece is when..
  • Open AI for Paul to post Doodle
• AMM (short of time)
  • Paul: We have CVII Tech Stack slots in the draft schedule. We need to decide if they are wanted and what the topics are.
  • AI: A wiki page will be created to work on the detailed Tech Stack talks

2022-02-16

agenda:

• project recap
• extra meeting discussion
• dev org
  • recording task list
• AoB

Related projects walkthrough (every week):

Minutes:

• Extra meeting discussion
  • Steve: I emailed a proposal to the list
    

    • After the extra meeting discussion last week I thought of one proposal on how to run them. In the Hypervisor group we would have what we called "deep dive" topics. A meeting dedicated to a single subject. We could do the same for the extra meeting. It would be on a set day and time to be agreed for continuity. However it will only go ahead if a topic has been agreed ahead of time, in the regular meeting. This avoids the trap of unproductive meetings and allows people to be selective about their interests.

  • Ulf: I like it.
  • Paul also supports the idea.
  • No other proposals made,
  • When?
    • AI: Paul will put up a doodle to identify some options of when ppl are available
    • Old CCS time should be one option: 4pm CET Monday
    • Time zones. More than one time slot may be needed. Doodle might gives us a couple of options from which we could select depending on topic participants.
  • Why?
    • Ulf: Integration of CCS scope including PoC for tech stack and CCS architecture diagrams.
    • Similar with Tech Stack work to date.
    • Anchoring discussions in shared architecture and terminology. Mapping prop
  • Naming
    • Weds: Tech Stack - eco-system/project coordination/sync
      • 1st half: recap
      • 2nd half: design work
    • New meeting: Tech Stack - detailed design
  • Topics backlog:
    • AI: Steve add page to add topic descriptions
    • (Alex) GraphQL implementation with VSS data feeders and storage. AI: Steve ask Alex to expand
    • Gunnar: Can translation is common request.
    • Gunnar: Refer CVII component list, e.g. protobuf, grpc.
    • Steve: Interfacing VSS Data Storage to VSS Data Servers
• Dev org
  • JIRA tickets
    • List things people can pick-up
    • In-progress collaborative development, e.g. VHAL project showing what tasks are planned, which in turn defines when work is done.

2022-02-09

Related projects walkthrough (every week):

Apologies:

• Sebastian S (Bosch)

Minutes:

• Project coordination

• Android VHAL

  • Ted: W3C talking to Google Cloud ppl. They want to learn more about VSS to AOSP VHAL properties converter. Who to loop in to explain to them?

  • Paul: Loop me in.

  • Gunnar: Stefan from TietoEvry leading the work.
• VSC
  • Heads up on discussions in VSC call.
  • Followed by illustration from Gunnar on specifying protocol and access control for VSC APIs and mapping the latter to existing systems, e.g. in GraphQL and VISS.
• Extra meeting
  • Continue discussion of whether to repurpose the CCS meeting into a wider CVII Tech Stack meeting dedicated to deep diving design discussions. Do we do want to do it? If so when?
  • Ulf, Steve would like to see it continue. Alex is interested but is time constrained.
  • Two CVII Tech Stack meetings:
    • Weds: CVII Tech Stack: project coordination
      • This call. Coordination update as already done, followed by general discussion with time remaining.
    • TBD: CVII Tech Stack: detailed design
      • New call. Scope is deep dive on tech stack topics not specific to the VSS, VSC specific calls. Engineering focus. Will be small # of topics, known in advance.
    • AI: Create Doodle for timing
  • Deep dive topic list:
    • Alex: Discussion of connecting VSS Data Store to GraphQL
• Remaining 10 mins:

  • Southbound x2VSS conversion and code generators

    • Outline of two methods we currently have for conversion:
      • Android VHAL design pattern using JINJA template and yaml conversion description
      • vss-otaku is looking at a varient to the VHAL pattern that uses VSS vspec rule set to define the source data model. Outcomes will include pluses (vss-tools function set) and minuses (need to avoid polluting VSS standard catalog with source data types and units) of that approach.
    • We expect to need to expand the VSS Terminology set to include converters and generators. Please consider what they should be. A good set will ease coordination in and outside the group.
  • In-vehicle VSS Data Store

    
    

    • Steve outlined the direction of travel for VSS Data Store investigations in vss-otaku
    • Some universal themes to investigate collectively for Tech Stack such as connections between VSS Data Feeders, Data Stores and Data Servers.
    • Alex: I would really like to have a deep dive on the VSS Data Store and how it relates to what we are doing with GraphQL. To share our viewpoint and align.
    • Steve: Would love to. Your production/OEM perspective would be invaluable to guide later work connecting Data Stores to Data Servers.
    • Steve: This would also be a perfect topic for the proposed CVII Tech Stack Detailed Design meetings. Added it as a starting topic above.

...

2022-02-02

Related projects walkthrough (every week): SKIPPED

Apologies

• Ulf, Thomas, 

Agenda / Minutes

• Project updates (skipped this week)
• New person introductions
  • Andreas Warnke (EB)
  • Alan Freedman (Autonomic/Ford)
  • Dimitri (Zync)
• Meeting structure
  • VSC - Vehicle Service Catalog - IDL language and catalog content
  • VSSo and VSS meeting - Vehicle Signal Specification - VSS model / catalog-content
    • + VSSo breakouts
  • CCS (not currently, restart or replace?)
  • W3C Automotive and Transportation WG 
    • Primarily working on VISS but it is starting to be complete → new topics come up
  • CVII Tech Stack (this meeting)
    • Reports/Updates on all projects 
    • Technical architecture and software discussions, solving problems
    • + Breakout meetings when the need comes up
      
      
• Service definition (VSC) in comparison to AOS service definition format
  • Service API definition
    • Improve the description of data-services in the service definition format.
    • Related aspects: resources, device, permissions
      → CVII related sub-tasks that we ought to work on:
    • Better description of which protocols are used
    • ... and the exact interface if it is a RPC protocol (i.e. reference a "VSC interface")
    • ... and a common methodology for permissions definitions.

permissions: 
   vis:
      Attribute.Body.Vehicle.VIN : "r"
      Attribute.Body.Vehicle.VIN : "r"
  

• VSS data protocols
  • Methods, access control etc
• VSS Data Stores
  • VSS Data Server backend abstraction layer possible?
  • Comms between zone controllers
    • DB data (sync, replication, partial send) vs Data Server protocol (e.g VISS)
      
      

...

Wednesday 2022-01-26

Related projects walkthrough (every week):

Project	Person reporting	Updates
Kuksa.VAL	Sebastian (Bosch)	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   Ted as backup	No discussion about spec (presentation MongoDB instead)
VISS server implementation in Go	Ulf	Nothing this week.
VSS & Tools	Daniel Wilms (BMW) (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:

• CVII Tech Stack
• Towards CVII pluggable components
• CVII Tech Stack Terminology

...

Wednesday 2022-01-19

Related projects walkthrough (every week):

Project	Person reporting	Updates
Kuksa.VAL	Sebastian (Bosch)	Upgrade CI infra to GH actions
W3C VISS specification (v2)	Ulf   Ted as backup	Feature freeze agreed.  Polishing ongoing.  W3C process steps.
VISS server implementation in Go	Ulf	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".
VSS & Tools	Daniel Wilms (BMW) (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	ovds-client (VISS client) updated to also support protobuf feature.
AOS	Artem	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

• CVII Tech Stack
• Towards CVII pluggable components
• CVII Tech Stack Terminology

Wednesday 2021-12-22

Project	Person reporting	Updates
Kuksa.VAL	Sebastian (Bosch)
W3C VISS specification (v2)	Ulf   Ted as backup	All open questions have been resolved (for the moment)
VISS server implementation in Go	Ulf
VSS & Tools	Daniel Wilms (BMW) (Gunnar, Sebastian as backup)	Meeting series postponed until January
VSSo	Daniel W   Ted	(See previous week)
VSC & Tools	Gunnar	Meeting series postponed until January
CCS-components	Ulf	--
AOS	Artem	Publishing has started on GitHub, and is still ongoing
Android Automotive VSS→ Vehicle Properties Code Generator		"Simple compile check" in CI system (stubbed out dependencies). See GitHub actions, currently on this branch here for example. Updated to generate all type=conversion functions on the fly.  Track Manu's vss-tools fork / PR for status.
Eclipse Kanto (proposed.  worth tracking in CVII call?)		not discussed today

Apologies

Ulf Bjorkengren 

Agenda/Minutes: 

• Project updates, see above.
• BMW / GraphQL – end 2 end demo
  • https://github.com/COVESA/graphql-vss-data-server is the latest repo (see also related ones).
  • Still to come:  Code generator from GraphQL schema itself.  Classes (stubs) that are implemented by the developers to make the binding connections.
  • The demonstration and part of the discussion was recorded for future use (link pending)
•  Reminder to review Towards CVII pluggable components, and CVII Tech Stack Terminology to give feedback
• Also the CVII Tech Stack components area (presented last week)

Wednesday 2021-12-15

• https://github.com/slawr/vss-otaku

• https://drive.google.com/file/d/1kVXB7bdTarzQdiwtZyNqCK-vHihJeW0w/view?usp=sharing

Wednesday 2021-12-08