Page History

...

Monday 2021-03-01

US friendly time 16:00 CET

Agenda

• alignment of Sensoris and VSS data model
  
• review of tickets related to the deployment of CCS communication framework  on cloud infrastructure
• sprint review and update

Participants

• Kevin, Ulf, Iyyaz, Irfan, Christian H, Ted, Stephen L, Gunnar, Philippe

• apologies: Benjamin

Minutes

quick roundtable

• Irfan is a new participant working for llts, Irfan is based in Bangalore, India, https://www.ltts.com/
  

alignment of Sensoris and VSS data model

• Jira
  server JIRA serverId 121ddff2-c571-320f-9e4d-d5b9371533bd key CCS-195

  Benjamin reported about the review he made prior to the call
  • Benjamin reviewed the slide deck shown at the CVII workshop (slide deck is here)

  • Some feedback on the slide deck shared:

    The overlap of signal categories is clear, Sensoris has both internal and external signals where VSS only has internal ones. What could complete this is that:

    • VSS only defines signals as things that your car senses/controls, not necessarily abstract information. For instance, the signal WindCondition does not exist in VSS but something equivalent could exist.
    • VSS orders signals by vehicle branch (part, component), while Sensoris has an approach based on use cases

    I believe these are the "notable differences" mentioned in slide 5.

    The proposals for collaboration are pretty clear and extensive. I would also include the possibility of organizing a workshop with developers of both community trying a set of use cases with a combination of both specs to find out where practical overlap/conflicts would happen. Another possibility is to have a spec importing the other (e.g. Sensoris using the VSS signal list like a catalog, translated into protobuf and Sensoris messages).

  • TODO Gunnar to forward Benjamin's inputs to Stefan Werder who at Bosch is working on the alignment of Sensoris and VSS data models, ticket rassigned to Gunnar

review of tickets related to the deployment of CCS communication framework  on cloud infrastructure

• Jira
  server JIRA serverId 121ddff2-c571-320f-9e4d-d5b9371533bd key CCS-101

  • Kevin: presents the analysis made by High Mobility on using terraform (please look at the comprehensive comment added to the ticket)
  • Gunnar/Philippe: this sounds like a plan
  • Gunnar:  what would happen if we change the database (like to a pure sql database) ? some parts of the demo use REST interface, however some part of OBDII interface should be changed, Ulf agrees

• Jira
  server JIRA serverId 121ddff2-c571-320f-9e4d-d5b9371533bd key CCS-189

  • Iyyaz: at Cobrasphere, we tried to build CCS and we have not succeeded yet

  • Iyyaz: it seems that ubuntu 10.x does not support some features

  • Gunnar:  that kind of things happen when you are not using ubuntu long term support

  • Iyyaz: would it be ok to use Alpine Linux ?

  • Gunnar: yes it is possible

  • Ulf: I know that Magnus Gunnarsson at Melco (who works in W3C) uses the Alpine distro

  • Iyyaz:  we will try to rebuild then

  • Gunnar: modifications should be made as pull requests

• Jira
  server JIRA serverId 121ddff2-c571-320f-9e4d-d5b9371533bd key CCS-192

  • Glenn: the challenge is to show the interopErability of the Geotab analytics tools with CCS

    
    

  • Ulf: explains the update made in the vehicle client component, we have a solution for transporting VISS onto of mqtt

  • Ulf: we use moskito server for this purpose

  • Stephen L: big picture is out of date in the wiki

sprint review and update

>>>>>>>>>>>> INSERTION POINT

Monday 2021-02-22

US friendly time 16:00 CET

...