Main thread: External Data Server Proof-Of-Concept - Work Breakdown Structure
Next Meeting - Virtual Technical Summit VHAL Workshop - Wednesday, May 13 15:00-18:00 CET
Following Meeting - Tuesday 19 May - 17:00-18:00 CET
Dial by your location: find your local number here
...
Tuesday 5 May - 500pm CET
Participants
- Alex, Johan, Piotr, Stefan, Sachin, Gunnar, Philippe
- apologies: JLR folks
Agenda
- VSS feeder update: connecting the graphql schema
- virtual meeting status report & workshop preparation
- AOB
Minutesroundtable
VSS feeder update: connecting the graphql schema
- Stefan: was able to put the graphql at work , I have a problem with the docker setup and the simulator that runs outside the VM
- demo can be shown as first milestone, i.e. at the virtual tech summit workshop
- Stefan will contact gunnar after
- Stefan: shows the set up of this demo and explains the problem he has with the nxtworking between the VM and the simulator that runs on windows
- Philippe: why don't you the GVS (GENIVI Vehicle Simulator) that runs on linux ?
- Stefan: we should use at a later stage a "better" database like SQL for instance
- Gunnar: can you all take into account the packaging, like we did in other projects where we use a docker setup ?
- Alex: I am fine with the docker packaging
virtual technical meeting - workshop preparation
- Alex: I had a call with Stefan yesterday, I do not know how deep we need to address the topics, let us do a brief overwiew of the topics
- topic #1 - VHAL implementation based on the graphQL implementation
- Google requires OEMs to implement properties in the Google way
- we want to deliver these properties outside the graphql server
- I hope to have JLR working on the proof-of-concept implementation with us, then we need to identify which workpackages need to be implemented
- Philippe: JLR people are shutdown for the month of May and will not show up again until next month, it is a good idea to prepare an updated work breakdown structure
- topic #2 - permission group
- Alex: this is about the concept introduced by Gunnar about the VSS layer concept; I would like to have a discussion on which concept we will follow in the future
- Alex: in our architecture we have different players, player 1 is the app, player 2 is the authentication service that generates the token, player 3 is the dataserver
- Alex: I intend to present my understanding of what I have learned about permission management
- topic #3 - graphql schema
- Alex: I generated the graphql scheima for the GENIVI VSS standard tree (on github)
- there is a private area for each and every OEM has his own branch
- do we need an additional layer to be integrated into the graphql schema ? or do we create empty leaves in our schema ?
- Gunnar: we need both actually
- Alex: do we talk about the generation process at the workshop ?
- Gunnar: I would like to invite you, Alex to partiicpate to W3C call on VSS call this evening
Tuesday 21 April - 500pm CET
...