Page History

...

Monday 2021-02-22

US friendly time 16:00 CET

Agenda

• debriefing of CVII workshop and next event
  
• CCS workplan
  • CCS communication framework  on cloud infrastructure

Participants

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

Minutes

debriefing of CVII workshop and next event

• workshop was a little bit too demanding (not enough breaks) but content was very good
• Christian liked eSync presentation and Iyyaz's talk on the deployment of CCS communication framework on cloud services infrastructure
• Iyyaz: woud have appreciated more time to explain the work and show demo
• Philippe: next major dissemination event will be the All Member Meeting scheduled on May 4-7, 2021
• Philippe: event will include a business track and technical tracks, there will be more time discussion and demos
• Christian H: forwards the link to the press release made by Bosch and Microsoft on Thu 18 February - https://www.bosch-presse.de/pressportal/de/en/bosch-teams-up-with-microsoft-to-develop-software-defined-vehicle-platform-for-seamless-integration-between-cars-and-cloud-224832.html
• Philippe: we have been talking to Microsoft for quite some time and we have scheduled a call with them later this week to talk about the Digital Twin Consortium
• Christian H: underlines that in his opinion the two companies also plan to use GitHub’s fully integrated enterprise platform and to open-source important parts of the new software platform on GitHub.com to encourage code re-use and best practice sharing across the industry.
• Christian H: why don't we use github that belongs to MS as our CI & testing environment e.g. by using https://github.com/features/actions

CCS workplan

• Philippe: shows the Jira tickets related to the deployment of CCS onto the cloud services infrastructures,

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

  and its subtasks

• Christian H: will speak to the Bosch team during our internal steering committee meeting on Thursday and underline the deployment of CCS on a cloud service infrastructure

• Ulf: I will do the same for google and google cloud environnement

• Iyyaz: are you talking about the devops cycle ? Christian: yes

  • discussion between Iyyaz/Christian on the development cycle and the release branching process

• Kevin: supports the idea of using AWS, we should split the branches among AWS, IBM, Google, MS Azure if we do the deployment ourselves

• HM is looking at Teraform (https://www.terraform.io/) and expects Teraform will facilitate the deploymnent on various cloud infrastructures

• Philippe recaps the actions for participants as described in the following set of Jira tickets

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

    Kevin: I will check with HM team whether they can provide a feedback on using teraform

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

    Iyyaz: will look into it this week

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

    this is also assigned to Iyyaz, but it would be interesting that Gunnar and Philippe check how MS can help for the deployment on MS Azure

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

    Ulf: will check with Geotab team whether they can provide support for deployment CCS on Google cloud services

Monday 2021-02-15

US friendly time 16:00 CET

...