Production Deployment¶
To deploy to production please got to the Bitbucket DPS Pipelines and click "Run Pipeline", pick the branch you wish to deploy (usually a release candidate branch rc/yyyy-mm-dd) then select the pipeline you would like to run - custom: production.
First the pipelines will build an "artifact", which then gets copied (rysnc) to Positive Internet, and finally the "deployment script" runs. This script makes sure each box gets the latest copy of the code and waits for success until moving on to the next box.
If you check the pipelines and click the 3rd step "Run positive deployment script", and scroll to the bottom you should get a summar similar to this output:
PLAY RECAP *********************************************************************
cubed-dcs-a : ok=6 changed=4 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0
cubed-dcs-b : ok=6 changed=4 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0
Note
It is possible to have a successful pipeline (all green), but there be a failed=1 in this output. If that has happened you will want to contact Positive Internet and provide them with the output from this pipeline's log. Chances are it couldn't connect to the server, or something has gone wrong while running the playbook on their system.
DCS Checks¶
Once deployed you can check in grafana and see that we're still processing and inserting.
DCS Buffers
It's quite common to see the DCS buffers increasing after a deploy, this is 99% of the time be fixed by updating the updated stamp in attrib.attrib_account for the active clients (race condition issue). We also sometimes see the buffers increasing for older accounts which are no longer active - please check the DCS logs to find which account is causing the buffers to increase and update updated.