Next Meeting -
...
10 March 5:00pm CET
...
Agenda items (to be prioritized at the beginning of the call)
- authentication implementation plan (work sharing between BMW & TietoEVRY)
- graphql and nodeJS installation
- project plan update - filling workitem description and definition of done
- discussion on proof-of-concept resourcing
- AOB
Backlog
Expand Backlog
- Android Compatibility Definition Document
- Software architectural task force : Vehicle Data architecture for Android
- Comparison of how vehicle properties are managed by Android 9 and 10 (Q) - further inputs
- question to address in the group: what do participating companies intend to do with the JAPI (Java API similar to CommonAPI for Android) ? this building block is currently missing
- Signal to service translation
- Secure access control in Some/IP
Tuesday 3 March - 500pm CET
Participants
- Alexander, Sachin, Andrii, Stefan, Piotr, Johan, Stephen, Gunnar, Philippe
Agenda
- project plan update - filling workitem description and definition of done
- proof-of-concept implementation resourcing
- AOB
Minutes
proof-of-concept implementation resourcing
- Stephen: can provide support for the R-Car target board and Lava test farm
- Gunnar: since we intend to use graphql technology for the VSS data server component, this is off-the-shelf
- Sachin: it is difficult to get support from internal teams, I need to involve open source people at Daimler, I need two more weeks before providing feedback
- Stefan: presents TietoEVRY proposed contribution
- Stefan: we will use the Android emulator and AOSP 10.0 for this development
- Gunnar: FYI Stefan's code was merged in the development branch
- pull request: aasig_dev_platform/pull/1 repository
Stefan: this work was mostly related to a former approach than the External Data Server (EDS) - Alex joins
Authentication
- 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
- 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 to clarify with Stefan what could be the contribution of Tieto to the authentication mechanism implementation
VSS feeder
- Alex: the scope of work depends on how much simulation we want
- discussion on how to implement the VSS data base in a limited manner for the purpose of demonstrating the concept
- Gunnar: for settting the values, would you suggest to use nodeJS code first ?
- Alex; yes, later we will use someip and so on
- Review of other work items for the VSS feeder
- todo finalize permissions layer concept (independent work item)
- Gunnar: we target a simpler mode of permissions, not a high priority
- todo create a layer concept for the Franca to VSS leaf mapping (model transformation)
- not a high priority
- todo check signal to service translation in Adaptive Autosar
- not a high priortiy
- todo agree on PoC use cases for the implementation
- Alex: this is important for the purpose of concept demonstration,
- Philippe: proposes to schedule this work item for next Sprint starting early April
- todo finalize permissions layer concept (independent work item)
Tuesday 18 February - 5:30pm CET
...