1536458 - Deploy mapper.mozilla-releng.net service on GCP

Status: RESOLVED FIXED

(Cloud Services :: Operations: Miscellaneous, task)

Description

[Rok Garbas [:garbas]]

I would like to migrate mapper.mozilla-releng.net from heroku to GCP managed by cloudops team.

Docker images are already created and waiting for deployment to GCP. Here I'm listing the docker tags used for different channels:

• mapper_api_dockerflow_production
• mapper_api_dockerflow_staging
• mapper_api_dockerflow_testing

Please use the same deployment configuration as we configured shipit/api project, this means that above docker tag:

• mapper_api_dockerflow_testing should trigger deployment to testing environment
• mapper_api_dockerflow_staging should trigger deployment to dev environent
• mapper_api_dockerflow_production should trigger deployment to stage and prod environment

Currently limitation on Heroku that we are hitting is that one of the API endpoints is reaching 30 second response limit and we need to raise this limit to 60 seconds.

Once instances are up and running I will switch testing and staging domains to GCP and test that everything is working correctly. Once testing and staging environment are working, I will switch production domain to point to GCP.

Did I miss any other details that is important?

Comment 1

[Rok Garbas [:garbas]]

I forgot to mention two things:

• a postgresql database in the backend
• configure 4 system variables:
  • DATABASE_URL (db connection string)
  • TASKCLUSTER_SECRET (the same as in shipit/api)
  • TASKCLUSTER_CLIENT_ID (the same as in shipit/api)
  • TASKCLUSTER_ACCESS_TOKEN (the same as in shipit/api)

Comment 2

[Rok Garbas [:garbas]]

this is now done:

• mapper.mozilla-releng.net
• stage.mapper.mozilla-releng.net
• dev.mapper.mozilla-releng.net