Page History

...

• 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 environnementenvironment

• 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

...