Page History

...

• review of epic

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

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

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

    • State storage is actually implemented using SQLite in the demo delivered at the AMM, ticket comm"nted and closed
      
    • TODO Philippe to poke Keith on the liaison with Autosar, there is a need for a translation from Autosar to VSS
    • Philippe: an alternative contact for Autosar might Christian H.

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

    • SQLite ias accepted and used in production alreafy, do we have alternatives ?

    • Ulf: some years ago, JLR develop something called VSI (on genivi github) that relied on shared memory

    • Gunnar: in some sense it is a kind of library, relevant to state storage

    • links in github

      • vehicle_signal_interface repository
      • vehicle_signal_manager repository (might be worth having a look at this too)

    • TODO Ulf to have a quick look at VSI, ticket assigned to Ulf

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

    • there is a need to reactivate the discussion with Sebastian and Bosch in general
    • TODO Philippe to poke Sebastian, ticket commented

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

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

      • Gunnar: it would be good to demonstrate with thousands of vehicles to show the performance

      • Ulf: agreed

      • ticket assigned to Gunnar, Ulf will help adapting the go code in the server (postgres)

      • note: postgres is an option, influx DB is another option

        
        

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

      • need to poke Glenn about it ?

      • ulf: would rather cancel it

      • ticket closed ac CANCELLED

  • review of backlog suspend suspended at

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

review of workbreakdown structure

• entry #1 - In-vehicle State storage : technonology choices for proof-of-concept and production-grade updated, see Jira tickets
• entry #4 - In-vehicle Data server : technonology choice for proof-of-concept updated (Gen2 implementation now uses ovds.db file. On-demand requests are fetched from database. Timed subscriptions are also supported, i.e. send updates at regular intervals.
  • There is not yet implementation of a trigger to the gen 2 server from the database when a new value is written (SQLite supports trigger in theory).
• entry #8 - OEM cloud access management :

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

  is a large piece of work
• entry #9 - OEM cloud resource management: we still use the manually generated graphql schema
  • Gunnar: the update of the graphql schema is still to do, will poke Daniel (BMW) on this
  • a new ticket is to be created for tracking the connection between graphql and ovds,

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

    created
  • entry #10 - neutral data server marketplace

AOB

• CVII working session follow up
  • Renault, Huyndai: Gunnar
  • Ford, VW: Philippe
• Gunnar proposes to update a table in the internal wilki we used when we prepared the AMM which is agreed

Monday 2020-11-2

US friendly time 16:00 CET

...