About these release notes
If you run your own CommCare instance, these release notes are for you. As always, see http://dimagi.github.io/commcare-cloud/changelog/ for the most up to date release notes and release note history.
These release notes are not simply for your information, they are instructions for you to follow.
Each change includes manual steps for you to follow to apply changes to your environment configuration or infrastructure that will allow you to be on the latest versions of commcare-cloud and commcare-hq.
Inside the instructions for applying the maintenance for each change, it will tell you whether there are any environments it may not be necessary for. When in doubt, apply the steps for every change.
2019-02-27 Remove celery results backend from localsettings
Upgrading to celery 4.x requires removing the dependency on django-celery, which means that its results backend will no longer be available. This removes the django-celery backend as the default from localsettings, so the results backend can be specified by commcare-hq settings instead.
2019-02-26 Split pgbouncer vars from postgresql vars
This change extracts a new role from the existing postgresql role for installing and configuring pgbouncer.
As a result of this change the
postgresql.ymlenvironment configuration file needs to be changed to split out the postgresql vars from the pgbouncer vars.2019-02-27 Only monitor specific RabbitMQ queues
Datadog RabbitMQ monitoring restricts the number of queues it can monitor to 200. To avoid hitting this limit on large scale deployments we limit the queues being monitored to only the primary queues.
2019-02-22 Update supervisor confs to invoke celery directly
Upgrading to celery 4.x requires removing the dependency on django-celery, which means that the celery management command becomes unavailable. This prepares for that by invoking the celery command directly.
2019-02-22 Separate celery datadog http check
This adds a specific http check for the celery check (serverup.txt?only=celery) to datadog. Environments that are not relying on datadog for monitoring can ignore this change.