...
External Data Server Proof-Of-Concept - Work Breakdown Structure
Tuesday 24 March - 500pm CET
Participants
- Alex, Stefan, Piotr, Johan, Nadim, Bartosz Cichosz, Stephen, Philippe
Agenda
- authentication implementation (work sharing between BMW & TietoEVRY)
- graphql and nodeJS installation
- staffing the EDS PoC (again !)
- AOB
Minutes
authentication implementation
- Alex: I was preempted by internal projects again, although I did some work on graphql
Stefan: we need to schedule a meeting
Alex: we can have a meeting on Thursday at 10-11:30am CET
Stefan: will send an invitation DONE
graphql and nodeJS installation
- Alex: I need to package what I have done in a container in order to make my work easy to reuse
- Stefan: can you give us a snapshot of what you have done ?
- Alex: yes, Alex shows the schema representing the vehicle data he is using for the testing of graphql together with some queries
- Philippe: it would be good that team participants have a look at the Apollo GraphQL documentation to get more familiar with the approach: https://www.apollographql.com/
- /TODO/ all participants to look at the Apollo GraphQL documentation: https://www.apollographql.com/
Next week's All Hands call preparation
- Philippe: I may have to escalate the situation and report that AASIG VHAL team have difficulties to staff the poc
- (added offline): as in all collaborative projects, it would be good that each participant consider spending a little bit more time than attending the calls and reading the minutes, otherwise everyone gets the impression the work is stuck
- Stefan: point 13 of the WBS (Define GraphQL schema - what does it look like?) was actually done by Alex as he showed the schema today
- Alex: agreed, I have the schema but something is still missing
- Stefan: we need to have something to get started on the other work items
- Stefan: we need also to agree on the data format
- discussion follows on how to bootstrap the work
- Stefan: will work out some prototype code and show it at the next VHAL call
- Philippe: next week's call will be the AASIG All-Hands call on 31 March at 17:00 CET (watch out: there is a time change scheduled on 28-29 March in Europe)
- Philippe: next VHAL call will be scheduled on 7 April at 17:00 CET
Tuesday 17 March - 500pm CET
Participants
...
graphql and nodeJS installation
- Alex!: this is on my todo list for this week
...
- Philippe: we do not whether the Spring AMM will be physical or virtual; decision will be made soon by the GENIVI board of directors
- Philippe: however we are planning actively the content of the sessions; there will 6 sets of sessions
- looking forward
- AASIG projects on VHAL & Audio HAL
- Cloud & Connected Services projects on Vehicle Data Model and Vehicle2Cloud Communication Infrastructure
- CyberscurityCybersecurity
- In-vehicle payment
- Connected Vehicle Software Development
...
- Alex: we are using Apollo graphql server which needs an addition for web token management, and other stuff we are working on, I have discussed which contribution we could do with Markus
- BMW has the blue box on the right box (authentication) (look at the EDS architecture diagram)
- BMW has only the EDS implementation, not the Internal Data Server one
- Alex: the permissions are not yet what we need
- discussion on the work to do for the authentication and the access control groups
- Gunnar: we need to do a more formal description of things to be done for the authentication
- Alex: might be able to do some work in the next days, will try out my ideas on an actual implementation, as soon as I have something (next week possibly), I will generate some docs like ppt
- Alex: tooling is not clear for me yet, as soon as we agree on the way to specify things, we will talk about tooling and manifest generation
- discussion on the naming of artefacts
- Alex: we want to have a nodeJS graphql implementation running
- Alex: I can describe the nodeJS and graphql installation and the deployment of json files
- Gunnar: the wiki page for documenting tihs is AASIG: Implementation notes
- /TODO/ Alex to describe the nodeJS and graphql installation in the above wiki page
- Stefan: at Alex, since you have the authentication implementation under way, could you spent some time to describe what you have done so that we can identify the leftovers ?
- Alex: I can explain that, for instance we need a json web token implementation
- /TODO/ Alex & Stefan to clarify what could be the contribution of BMW & Tieto to the authentication mechanism implementation
...