1248759 - Define deployment process between releng and cloudops

Status: RESOLVED FIXED

(Release Engineering Graveyard :: Applications: Balrog (backend), defect)

Description

[Benson Wong [:mostlygeek]]

From the Onboarding meeting it was determined that there isn't a formal release process. :bwong suggest that we do this: 

- releng pushes a tag to github
- that will trigger circle ci to build / push a container to docker hub
- open a deployment bug in "Balrog: Backend" 
- ops will deploy a stage stack and do any DB migration required
- QA resource will test the stage stack
- ops will deploy a production stack using blue/green deployment:
  - canary deployed, single server getting part of prod traffic
  - scale up canary stack to full size
  - scale down previous stack

Let's discuss here if this process is acceptable.

Comment 1

[[e-mail] (:bhearsum)]

(In reply to Benson Wong [:mostlygeek] from comment #0)
> From the Onboarding meeting it was determined that there isn't a formal
> release process. :bwong suggest that we do this: 
> 
> - releng pushes a tag to github
> - that will trigger circle ci to build / push a container to docker hub
> - open a deployment bug in "Balrog: Backend" 
> - ops will deploy a stage stack and do any DB migration required
> - QA resource will test the stage stack
> - ops will deploy a production stack using blue/green deployment:
>   - canary deployed, single server getting part of prod traffic
>   - scale up canary stack to full size
>   - scale down previous stack
> 
> Let's discuss here if this process is acceptable.

This sounds fine, except s/circle ci/taskcluster/. The inputs and outputs from that step remain the same, so that shouldn't make a difference to y'all.

Comment 2

[Benson Wong [:mostlygeek]]

- Balrog containers are built in TaskCluster and pushed to Dockerhub
- Cloudops mirrors from DH and deploys
- Deployments require a deployment bug
- QA will be done by releng